| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Immediate shutdown and system(3) |
| Date: | 2009-03-18 21:12:58 |
| Message-ID: | 15785.1237410778@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Mar 18, 2009 at 4:40 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> The CVS commit message.
> Is there some reason we don't just put it in the release notes as
> *part* of the commit? Someone can always go back and edit it later.
That was suggested before, and I think we actually tried it for a few
months. It didn't work.
Putting an item in the release notes *properly* is a whole lot more
work than putting a short bit of text in the CVS log (especially for
committers whose first language isn't English). It would also
create a lot more merge-collision issues for unrelated patches.
It's less trouble overall to do the editing, organizing, and SGML-ifying
of all the release notes at once. Also you end up with a better
product, assuming that whoever is doing the notes puts in reasonable
editorial effort.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-03-18 21:31:26 | Re: Immediate shutdown and system(3) |
| Previous Message | Robert Haas | 2009-03-18 21:00:58 | Re: Immediate shutdown and system(3) |