Re: PG 19 release notes and authors

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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:42:52
Message-ID: CAKFQuwak+Q7s2Viw7wi=sp=p_OarRmvqCz7D19wSdrWDz4pODw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

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.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-04-06 14:44:33 Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
Previous Message Bruce Momjian 2026-04-06 14:30:58 Re: PG 19 release notes and authors