Re: Maintaining the list of release changes

Peter Eisentraut <peter_e@gmx.net> writes:
> Would it be too much to ask for that everytime a significant
> user-visible change is checked in, the release notes are updated right
> there as though they are documentation (which they are)?
>    Having the list reconstructed by a single person from CVS logs months
>    after the fact is just way too lossy.

I agree completely, and was about to make a similar proposal.  However,
I'm not entirely sure where "the release notes" actually are, nor which
is the master copy.  Also, I'd prefer not to have to deal with SGML
markup for them.

What I'd suggest is that we keep a plaintext file somewhere near the
top of the CVS tree (in doc/ perhaps) that developers append
release-notes items to as the work is completed.  At the end of each
development cycle, Bruce can prepare the "nice looking" notes from that
source and then reset the file to empty for the next cycle.
        regards, tom lane