Update the release documentation to take account of voting on releasing artificats, and also how to do that without ending up with artificats containing the wrong version numbers or dates

git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@540546 13f79535-47bb-0310-9956-ffa450edef68

src/documentation/Release-Checklist.txt

@@ -1,14 +1,34 @@
 Release Checklist
 -----------------
 
-- build distributions
-- sign distributions
-- Generate announcements and HEADER.html
-- upload distributions to correct dir
-- tag CVS
+- 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)
+- 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/
+- 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
-- send announcements to announcement@apache.org, announcements@xml.apache.org, announcements@jakarta.apache.org
+- 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