Re: [HACKERS] list of credits for release notes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] list of credits for release notes
Date: 2018-01-03 17:15:33
Message-ID: 20180103171533.GB28459@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 1, 2017 at 11:24:03PM -0400, Peter Eisentraut wrote:
> On 10/2/17 18:34, Bruce Momjian wrote:
> > My smaller question is how will this list be generated in PG 11? From
> > the commit log when the release notes are created, or some other method?
>
> I don't think it should be done at the same time as the release notes.
>
> Specifically, we have recently put an emphasis on having the release
> notes ready for beta, and the natural flow of things should be that
> there are relatively few changes to the the substance of the release
> notes once beta gets rolling. On the other hand, I have found that a
> significant amount of new contributors appear in commit messages during
> beta, which also makes some sense. So making the contributor list
> fairly late and then not changing it much is more efficient.

Sorry for the late reply. If you can create the contributors list
easily post-release-notes creation, all the better for me. Thanks. :-)
Creating the list during release notes creation would certainly be a
separate step, so you are right that creating them later when the list
is fully accurate is a good idea.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2018-01-03 17:30:28 Re: [HACKERS] SQL/JSON in PostgreSQL
Previous Message Joshua D. Drake 2018-01-03 17:08:59 Re: TODO list (was Re: Contributing with code)