Maintaining the list of release changes

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)? This immediately
leads to three significant advantages:

1. Users can keep track of developement.

Until after the start of beta, no user really had any idea what this
new release was going to be about. Users that started projects before
the release notes were in readable form were wasting their time, if
they chose PostgreSQL at all.

2. Developers can keep track of development.

The number of changes for 7.2 is really enough for five releases, but
no one can be expected to keep track of that. So in the future, when
the list gets too long, we make a release. ;-)

3. The list accurately reflects the actual work.

Having the list reconstructed by a single person from CVS logs months
after the fact is just way too lossy.

--
Peter Eisentraut peter_e(at)gmx(dot)net