Re: PG 19 release notes and authors - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PG 19 release notes and authors
Date
Msg-id adJn3nBX13YYRBJP@momjian.us
Whole thread Raw
In response to Re: PG 19 release notes and authors  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG 19 release notes and authors
Re: PG 19 release notes and authors
List pgsql-hackers
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  <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: Shinya Kato
Date:
Subject: Re: remove autoanalyze corner case
Next
From: Ashutosh Bapat
Date:
Subject: Re: Better shared data structure management and resizable shared data structures