From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
Subject: | Re: Postgres tracking - the pgtrack project |
Date: | 2006-09-02 16:00:59 |
Message-ID: | 200609021200.59376.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On Saturday 02 September 2006 11:42, Tom Lane wrote:
> BTW, another "output" thing you might consider is "having draft release
> notes ready-to-go on demand". Currently, Bruce prepares the release
> notes on the basis of a very tedious scan of the CVS commit logs.
> If this sort of stuff were being dropped into a tracker as it went
> into the CVS tree, at least the research part of making the notes would
> be zero-effort (or perhaps better to say that the work would be spread
> out instead of concentrated).
FWIW I have never understood why we don't require patch submitters/committers
to update the release notes when they do the patch. I know Bruce says that
it's not a problem for him to do it, but it sure would help out some of the
other folks.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-09-02 16:02:52 | Re: Postgres tracking - the pgtrack project |
Previous Message | Bruce Momjian | 2006-09-02 15:56:41 | Re: [COMMITTERS] pgsql: Allow PL/python to return |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-09-02 16:02:52 | Re: Postgres tracking - the pgtrack project |
Previous Message | Tom Lane | 2006-09-02 15:42:25 | Re: Postgres tracking - the pgtrack project |