Re: PG 19 release notes and authors
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Álvaro Herrera <alvherre@kurilemu.de>, Peter Geoghegan <pg@bowt.ie>, Andrey Borodin <x4mmm@yandex-team.ru>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-06T17:03:08Z
Lists: pgsql-hackers
On Mon, Apr 6, 2026 at 12:37:39PM -0400, Andres Freund wrote: > > Any changes to the wiki are going forward. While receiving emotional > > replies, I have not received answers to my specific questions. > Expecting detailed responses while other folks are working on getting stuff > committed before the feature freeze also seems like a bit much. And again, > that seems unrelated to the complain here that you're unilaterally making > decisions. Uh, I am also working on getting the PG 19 release note ready, so I at least needed to know what the PG 19 rules should be. I could not wait for after the feature freeze date. > > What is the answer, both for PG 19, and going forward? I need an > > answer because I need rules to follow. > > I think the answer is for you to roll back your changes, assume co-authorship > means co-authorship, and then, if you think we need another tag, start a > discussion about how what tag to use for "blame-but-no-credit-goes-to" going > forward. I would strongly recommend starting that discussion only once we're > well into the betas for 19, because it's just going to sow confusion if we > consider doing anything like this while still doing 19 stuff. Uh, just to clarify, these are changes made on January 8, 2025, and were discussed on pgsql-private-committers@lists.postgresql.org, that need to be changed: https://wiki.postgresql.org/index.php?title=Commit_Message_Guidance&diff=40351&oldid=40350 I have updated the text to now be: Used to indicate the patch authors. If no "Author" or "Co-authored-by" is listed, the committer is assumed to be the author. > > I don't have a strong opinion but I do think we need a syntax for > > committers to indicate they modified a patch, might have introduced > > bugs, but don't want release note author credit, since I think several > > people have found that useful. Is that inaccurate? > > I for one don't believe that's needed. Committers always are to co-blame for > stuff they commit, so when do you need to express blame-but-no-credit-goes-to? True. I don't really care what the rules are. I was only emailing to say what I thought the rules we agreed on last year don't match the commit messages, so I need to know the rules. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add tests for lock statistics, take two
- 557a9f1e3e62 19 (unreleased) cited
-
Introduce a new mechanism for registering shared memory areas
- 283e823f9dcb 19 (unreleased) cited