| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-core <pgsql-core(at)postgresql(dot)org> |
| Subject: | Re: [CORE] postpone next week's release |
| Date: | 2015-06-01 16:12:04 |
| Message-ID: | 556C8454.5070409@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/29/15 5:28 PM, Bruce Momjian wrote:
>> could expect that anyone committing a user-visible semantics change should
>> >update the release notes themselves.
> Yes, that would be nice.
FWIW, I've always wondered why we don't create an empty next-version
release notes as part of stamping a major release and expect patch
authors to add to it. I realize that likely creates merge conflicts, but
that seems less work than doing it all at the end. (Or maybe each patch
just creates a file and the final process is pulling all the files
together.)
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-06-01 16:32:21 | Re: [CORE] postpone next week's release |
| Previous Message | Tom Lane | 2015-06-01 13:38:40 | Re: [CORE] postpone next week's release |