From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Release notes |
Date: | 2006-09-15 14:42:18 |
Message-ID: | 24554.1158331338@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Well we could make it "edit release.txt" which someone will fix up and turn
> into release.sgml later instead.
> I think if you put a big enough separator between entries, say two black
> lines, two dashes, and two more blank lines, it wouldn't even cause merge
> conflicts if it failed -- it would just insert the new entry in the "wrong"
> place which wouldn't really matter.
> Or you could have a release-notes directory and create a small text file in
> there for each major patch.
Andrew had the correct perspective on this: if someone wants a different
release note process, and is willing to expend their *own* cycles on it,
go to it. If the intention is to try to force the existing committers
to expend extra effort for a process change they do not particularly
believe in, don't be surprised by a lack of cooperation.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rocco Altier | 2006-09-15 14:44:32 | Re: [PATCHES] Linking on AIX (Was: Fix linking of OpenLDAP libraries ) |
Previous Message | Andrew Dunstan | 2006-09-15 14:34:29 | Re: polite request about syntax |