Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> 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.
That is pretty much my objection, even though I have to spend the days to create release.sgml. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
