Re: PG 19 release notes and authors

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 15:03:57
Message-ID: adPLXU1Pf6TivcVq@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 6, 2026 at 10:56:49AM -0400, Andrew Dunstan wrote:
>
> On 2026-04-06 Mo 10:29 AM, Bruce Momjian wrote:
>
> I think having "Co-authored-by:" mean one thing when "Author" appears
> and a different thing when "Author" is missing is too confusing.
>
>
>
> Possibly. I think we're tying ourselves up in knots needlessly here, though. To
> me, without having to interpret the exact meaning by consulting a wiki,
> Co-authored-by signifies that the person made a significant contribution, but
> not as much as the Author(s). These things shouldn't be technical terms of art.
>
> Personally, I'm in favor of being fairly liberal about giving release note
> credits.

So "Co-authored-by:" shows a level of involvement, but doesn't have any
effect on the major release notes. That works too.

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2026-04-06 15:11:15 Re: pg_plan_advice
Previous Message Thomas Munro 2026-04-06 15:02:52 Re: Automatically sizing the IO worker pool