public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: Andrey Borodin <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: PG 19 release notes and authors
Date: Mon, 6 Apr 2026 10:29:57 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<xgwkagej6rzkxg235ol4vzq3dljvaumzk3lhfecld4hogl4od5@mq6jaccjoxvz>
<[email protected]>
<[email protected]>
On Mon, Apr 6, 2026 at 09:37:39AM -0400, Bruce Momjian wrote:
> On Sun, Apr 5, 2026 at 11:10:52AM -0400, Tom Lane wrote:
> > Andres Freund <[email protected]> writes:
> > > On 2026-04-05 16:09:57 +0200, Álvaro Herrera wrote:
> > >> On 2026-Apr-05, Bruce Momjian wrote:
> > >>> I just updated the wiki to handle this case because obviously
> > >>> Co-authored-by is listing more than just committers:
> >
> > > I think that is a completely unwarranted change for which there is zero
> > > concensus.
> >
> > Indeed. You exceeded your authority here.
> >
> > Even if there were consensus about making this change going forward,
> > the existing commit records were made under a different understanding.
> > You can't just say you're going to reinterpret them in a way that
> > excludes giving credit where credit is due.
>
> My email said:
>
> I need to know what to do for PG 19, and what to do for later major
> releases. I think Peter's point is why are people using Author
> and Co-authored-by in the same commits, and not just two Authors.
>
> Any changes to the wiki are going forward. While receiving emotional
> replies, I have not received answers to my specific questions.
I now realize the Commit Message Guidance used during PG 19 was unclear;
it was:
Used to indicate the patch authors. "Co-authored-by:" is used by
committers when they want to give full credit to the named individuals,
but also indicate that they made significant changes.
I doesn't really say we are giving credit to "Author" individuals but
list committers as co-authors with no credit, so that bad wording is on
me. It should have said:
Used to indicate the patch authors. "Co-authored-by:" is to list
committers when they want to give full credit to the "Author"
individuals, but also indicate that they made significant changes.
Again, we now need rules for PG 19, and for the future. It now says:
Used to indicate the patch authors. "Co-authored-by:" should list
individuals, particularly committers, who modified the patch but
should not be listed as authors in the release notes.
Again, that will be changed once we decide what we want.
I think having "Co-authored-by:" mean one thing when "Author" appears
and a different thing when "Author" is missing is too confusing.
--
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], [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