From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, 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 19:30:37 |
Message-ID: | 200609151930.k8FJUbm28116@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.
That is pretty much my objection, even though I have to spend the days
to create release.sgml.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2006-09-15 19:35:18 | Re: Optimize ORDER BY ... LIMIT |
Previous Message | Alvaro Herrera | 2006-09-15 19:23:42 | Re: Optimize ORDER BY ... LIMIT |