From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:31:48 |
Message-ID: | 8764fpqjzf.fsf@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Well, I'm willing to (and I think usually have) put release-note-grade
> descriptions into commit log messages, but I'm not willing to add "edit
> release.sgml" to the already long process, for two basic reasons:
>
> * it'd make release.sgml into a commit bottleneck --- if everyone is
> doing it this way, everyone's local copy of the file would be constantly
> out of date, and merge conflicts would be an everyday problem.
>
> * correct SGML markup is a PITA.
>
> If *someone else* wants to troll the commit logs every so often and make
> entries into release.sgml, that's fine with me. But I don't have the
> bandwidth.
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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-15 14:32:13 | Re: polite request about syntax |
Previous Message | Joshua D. Drake | 2006-09-15 14:30:49 | Re: polite request about syntax |