Date: Sat, 4 Apr 2026 22:33:54 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>,
	PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Subject: Re: PG 19 release notes and authors
Message-ID: <adHKEqIjxmoJ6blM@momjian.us>
References: <adElLtegJxi6Yecv@momjian.us>
 <D593F697-26B4-4ED0-B0D2-F1583ABB3B24@yandex-team.ru>
 <adGeZg1VP6UudpDd@momjian.us>
 <CAH2-WzmNPpvDc9EO9fvDJUnmE_ppZWwwwfxRBk7nybjEL8Y1=A@mail.gmail.com>
 <adHFKVgnSkXHRJQD@momjian.us>
 <CAH2-Wzk2okKGYEPjypnMZ+NMZHq5oz6etpxL9U-na7RwznKKvw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAH2-Wzk2okKGYEPjypnMZ+NMZHq5oz6etpxL9U-na7RwznKKvw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/adHKEqIjxmoJ6blM%40momjian.us>
Precedence: bulk

On Sat, Apr  4, 2026 at 10:29:15PM -0400, Peter Geoghegan wrote:
> On Sat, Apr 4, 2026 at 10:13 PM Bruce Momjian <bruce@momjian.us> wrote:
> > Yes, that was the original purpose.
> 
> I didn't actually know that. That's likely my own fault. (OTOH I
> haven't actually used the new tag at all, at least not yet.)

Yes, that is what I used it for in the past.

> > Basically, if a commit has no
> > "Author" tag, the committer is assumed to be the author.  If there is an
> > "Author" tag, the committer is not assumed to be the author.  If there
> > is an Author tag and the committer wants author credit, they must add
> > their name as an author.  If the committer wants to indicate they
> > changed the patch, and potentially added bugs, but doesn't want credit,
> > the wiki says to use Co-authored-by.
> 
> Got it. That makes sense to me (obviously, since I already said that
> that's the only policy that could possibly be useful).
> 
> > > What I'm saying here boils down to this: I don't think it's sensible
> > > to expect the use of a specific tag variant (or even the order in
> > > which author names appear) to convey much useful information. I really
> > > hope nobody reads too much into my choices in this area.
> >
> > Well, I don't care what we decide, but we should decide something.  You
> > can say they don't convey information, but I need to put something in
> > the release notes, so they are forced to have some effect.
> 
> I think that Co-authored-by should either: 1. have a specific
> mechanical purpose (like affecting how the release notes are written),
> OR 2. not exist at all.
> 
> What's the point, otherwise? It just doesn't make sense to have a
> Co-authored-by that merely conveys a general vibe. These things are
> inherently squishy and subjective. Pretending otherwise would be a
> mistake (to be clear I'm not suggesting that you or anybody else has
> made that mistake).

Yes, that was the argument --- Co-authored-by should have some purpose
because making it behave like Author has little value.

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