Re: Postgres tracking - the pgtrack project

On 2/9/06 16:42, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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).

We have the developers update the CHANGELOG file with each non-trivial
change in pgAdmin. It works very well for us and producing release
announcements etc. is a trivial task. The overhead on each developer is
virtually zero as well as they have to compose some text for the commit
message anyway.

http://www.pgadmin.org/development/changelog.php

Regards, Dave.