public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jim C. Nasby <[email protected]>
To: Dave Page <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: Postgres tracking - the pgtrack project
Date: Thu, 7 Sep 2006 14:33:05 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <C11F7E97.13196%[email protected]>
References: <[email protected]>
<C11F7E97.13196%[email protected]>
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 [email protected]
512.569.9461 (cell) http://jim.nasby.net
view thread (101+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Postgres tracking - the pgtrack project
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox