From: Robert Treat <xzilla@users.sourceforge.net>
To: pgsql-hackers@postgresql.org
Subject: Re: Postgres tracking - the pgtrack project
Date: Sat, 2 Sep 2006 12:00:59 -0400
User-Agent: KMail/1.9.1
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 "Greg Sabino Mullane" <greg@turnstep.com>
References: <621fdf7c380b797f32c1ac0f7bccffd4@biglumber.com>
	<3454.1157211745@sss.pgh.pa.us>
In-Reply-To: <3454.1157211745@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200609021200.59376.xzilla@users.sourceforge.net>

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