Re: PG 19 release notes and authors

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(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:53:03
Message-ID: adPIz8YwYId-ToEA@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 6, 2026 at 07:42:52AM -0700, David G. Johnston wrote:
> On Monday, April 6, 2026, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>
> I think having "Co-authored-by:" mean one thing when "Author" appears
> and a different thing when "Author" is missing is too confusing.
>
>
> The community hasn’t recognized intermediate contributions between authorship
> and reviewer.  Co-Author has always been available for technical reasons but
> doesn’t actually convey less status than Author even if some people intended it
> to be used that way.  I don’t think we should change that.  Stating it more
> clearly seems warranted.

Okay, I am fine with that, though it does not give committers any way to
indicate via tags that they changed the patch when they don't want to be
listed as author. They can just state that in the commit text.

> Co-authored never means any thing different than “one of the authors”.  It’s
> committed-by whose meaning changes in the presence/absence of author.  I
> likewise don’t see changing that.  For future users of this information, having
> a silent boundary at which the meaning/usage of labels changes is very
> annoying.

Uh, is this what people want, because it is at least logical and a rule
that can be followed.

--
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 Robert Haas 2026-04-06 14:55:02 Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
Previous Message John Naylor 2026-04-06 14:47:32 Re: PG 19 release notes and authors