public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Peter Geoghegan <[email protected]>
Cc: Andrey Borodin <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: PG 19 release notes and authors
Date: Sun, 5 Apr 2026 09:47:10 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<CAH2-WzmNPpvDc9EO9fvDJUnmE_ppZWwwwfxRBk7nybjEL8Y1=A@mail.gmail.com>
<[email protected]>
On Sat, Apr 4, 2026 at 10:12:57PM -0400, Bruce Momjian wrote:
> What confuses me are cases where Authors are not the committer and
> Co-authored-by are not the committer. This combination is not
> documented in the wiki, which makes me think people are using
> Co-authored-by in ways that are inconsistent or I don't understand.
I now realize I was treating non-committers listed as Co-authored-by the
same as committers being listed. Someone who is listed as
Co-authored-by made changes to the patch, perhaps adding bugs, but not
someone who should be listed as an author of the release note item.
I just updated the wiki to handle this case because obviously
Co-authored-by is listing more than just committers:
https://wiki.postgresql.org/wiki/Commit_Message_Guidance#Tags%3A_%22%3A%22
Used to indicate the patch authors. "Co-authored-by:" should list
individuals who modified the patch but should not be listed as
authors in the release notes.
I am not sure PG 19 follows this, but we might want to follow it going
forward.
A larger issue is that since we now have links to the commits in the
release notes, there might no longer be a need to list _any_ names next
to the release note items.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
view thread (53+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: PG 19 release notes and authors
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox