Re: PG 19 release notes and authors

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG 19 release notes and authors
Date: 2026-04-06 14:55:22
Message-ID: adPJWpAs8mKwFWue@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 6, 2026 at 09:47:32PM +0700, John Naylor wrote:
> > I think having "Co-authored-by:" mean one thing when "Author" appears
> > and a different thing when "Author" is missing is too confusing.
>
> My take is that the co-author tag has backfired and made things less
> clear. If we are using it inconsistently, then it doesn't convey any
> useful information. I'd actually rather just use "Author" exclusively
> and if there is some further detail that needs to be conveyed, it can
> be in the message body.

The original intent as I understood it was for "Co-authored-by:" to be
lesser authors, typically the committer, but as you said, we haven't
done that consistently in the past. Do we want to do it consistently
going forward or just not use "Co-authored-by:"?

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2026-04-06 14:56:49 Re: PG 19 release notes and authors
Previous Message Fujii Masao 2026-04-06 14:55:08 Re: client_connection_check_interval default value