On Sat, Sep 02, 2006 at 06:31:51PM +0100, Dave Page 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.
Another possibility would be to annotate commit messages that should get
added to the release notes and have something automagically cull those
out of CVS.
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net