Jim Nasby <jim.na...@bluetreble.com> writes:
> 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.)
There are good reasons to write the release notes all in one batch:
otherwise you don't get any uniformity of editorial style.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
