Re: First draft of PG 19 release notes - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: First draft of PG 19 release notes
Date
Msg-id aeD8ryt2uX8flDP8@momjian.us
Whole thread
In response to Re: First draft of PG 19 release notes  (Michael Banck <mbanck@gmx.net>)
List pgsql-hackers
On Thu, Apr 16, 2026 at 09:54:57AM +0200, Michael Banck wrote:
> > Well, I am guessing you didn't read this thread fully:
> > 
> >     https://www.postgresql.org/message-id/flat/adElLtegJxi6Yecv%40momjian.us
> >
> > This was specifically for "Co-authored-by:" == committer, but the text
> > was not clear enough.  However, that doesn't match your usage where a
> > missing "Author" is considered to be the committer.
> 
> I think if the committer omits an "Author" tag, but credits a
> non-committer as "Co-Author", then both the committer and the
> non-committer should be considered authors and credited in the release
> notes.
> 
> What would be the use-case for a sole non-committer "Co-Author" (as
> opposed to just crediting the non-committer as "Author") otherwise be?

I agree with you, and made that case in January of 2025 and in the email
thread URL above.  However, I seemed to annoy people more than help
them, so I am not going to revisit it.  If someone else wants to restart
that thread and get a different consensus, feel free to do so.

My guess is that most (vocal?) committers prefer to have Author and
Co-Author indicate different levels of authorship in the commit text,
rather than have them have different behavior for release note
authorship.

-- 
  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.



pgsql-hackers by date:

Previous
From: SCHOEMANS Maxime
Date:
Subject: Re: Implement missing join selectivity estimation for range types
Next
From: Bruce Momjian
Date:
Subject: Re: First draft of PG 19 release notes