| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | 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: list of credits for release notes |
| Date: | 2017-11-02 03:24:03 |
| Message-ID: | 29bffb8b-2bba-7b9f-85da-f80ff6234af3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-11-02 03:27:46 | ucs_wcwidth vintage |
| Previous Message | 高增琦 | 2017-11-02 03:13:32 | Re: Try to fix endless loop in ecpg with informix mode |