FYI, hadoop generates their release notes automatically: http://wiki.apache.org/hadoop/HowToRelease see item 3 of "updating release branch"
while not perfect (it only includes information on issues addressed in the release) it has the benefit of capturing more detail while a release is evolving (in the "release notes" field of the jiras) rather than waiting till the end. You could also combine this with a static release notes file that's updated during the development cycle. Patrick On Thu, Mar 22, 2012 at 7:08 PM, Juhani Connolly <[email protected]> wrote: > +1 > > One reservation I have is that it would be nice to document pitfalls in the > release notes, stuff that we know that doesn't work. Mainly running > reconfiguration. > > > On 03/19/2012 05:45 PM, Arvind Prabhakar wrote: >> >> This is the second incubator release for Apache Flume, version >> 1.1.0-incubating. >> >> *** Please cast your vote within the next 72 hours *** >> >> The list of fixed issues: >> >> https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc0/CHANGELOG >> >> The tarball (*.tar.gz), signature (*.asc), checksum (*.md5sum, >> *.sha1sum) for the source and binary can be found at: >> >> http://people.apache.org/~arvind/flume/110rc0/ >> >> The tag to be voted upon: >> >> https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc0/ >> >> The KEYS file: >> http://www.apache.org/dist/incubator/flume/KEYS >> >
