From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | 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 13:52:02 |
Message-ID: | 24063.1158328322@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Neil Conway <neilc(at)samurai(dot)com> writes:
> Bruce Momjian wrote:
>> How is maintaining another file on every commit going to go over?
> Well, it would clearly not be on every commit: most commits don't
> warrant a mention in the release notes. If committers think that this
> burden is too much to bear, please speak up.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ricardo Malafaia | 2006-09-15 14:08:13 | polite request about syntax |
Previous Message | Tom Lane | 2006-09-15 13:41:01 | Re: [ADMIN] Vacuum error on database postgres |