Release Checklist
-----------------

- ensure the changelog is up to date
- tag SVN
- build distributions as if it was the final release
- update any filename dates from today's date, to the date that the
   vote will end (typically 7 days time)
- copy the -redirect pom to a subdirectory of redirect/, and remove
   -redirect from its name
- sign and checksum distributions as per
    http://www.apache.org/dev/mirror-step-by-step.html
- upload to your area of people.apache.org under /<version>-RC-<x>/
   (eg 3.0.1-RC-2)
- add a README.txt to the directory that states the files are a
   release candidate pending a vote, despite their name being -FINAL
- include the URL of this in the release vote (goes to dev, not user)
   (eg http://people.apache.org/~nick/3.0.1-RC-2/)

- wait for release vote to pass
- send notification of vote passing to private@

- move distributions from your area of people.apache.org to the 
   distribution directories on www.apache.org/dist/poi/ and
   people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.poi/
- move the redirection pom from your area of people.apache.org to
   people.apache.org/repo/m1-ibiblio-rsync-repository/poi/poms/
- copy the new distributions to archive.apache.org
- remove the old distributions from www.apache.org/dist/
- wait for the distributions to appear on your favourite mirror

- generate announcements
- generate www pages and upload
- bump release ID in build.xml
- send announcements to user and dev lists
- send announcements to announcement@apache.org, announcements@jakarta.apache.org
- news to newsgroups: comp.lang.java.softwaretools
- post stories on
  *) jakarta news page
  *) theserverside.com
  *) freshmeat.net
  *) www.javaworld.com
  *) www.javalobby.com
  *) www.jguru.com
  *) www.slashdot.org
  (and follow them up)