Re: PG 19 release notes and authors

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-04T23:27:34Z
Lists: pgsql-hackers
On Sat, Apr  4, 2026 at 11:18:33PM +0500, Andrey Borodin wrote:
> 
> 
> > On 4 Apr 2026, at 19:50, Bruce Momjian <bruce@momjian.us> wrote:
> > 
> > In the PG 19 commits, I am seeing several commits with Author and
> > Co-authored-by tags.  FYI, I think we agreed that only the Author names
> > are mentioned as the authors in the release notes.
> 
> Speaking of co-authors - I think they absolutely should be included in the
> release notes credits.
> 
> The more recognition we give contributors, the more motivation newcomers
> have to join the development community. There are edge cases where a feature
> gets reverted in a later minor release, but those are rare. What matters
> is that we need a steady stream of new contributors, and crediting everyone's
> work - including co-authors - is one of the most effective ways to
> encourage that.

This is the same argument we have had for ages, accuracy vs
encouragement.

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



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add tests for lock statistics, take two

  2. Introduce a new mechanism for registering shared memory areas