4 - ensure the changelog is up to date
6 - build distributions as if it was the final release
7 - update any filename dates from today's date, to the date that the
8 vote will end (typically 7 days time)
9 - copy the -redirect pom to a subdirectory of redirect/, and remove
10 -redirect from its name
11 - sign and checksum distributions as per
12 http://www.apache.org/dev/mirror-step-by-step.html
13 - upload to your area of people.apache.org under /<version>-RC-<x>/
15 - add a README.txt to the directory that states the files are a
16 release candidate pending a vote, despite their name being -FINAL
17 - include the URL of this in the release vote (goes to dev, not user)
18 (eg http://people.apache.org/~nick/3.0.1-RC-2/)
20 - wait for release vote to pass
21 - send notification of vote passing to private@
23 - move distributions from your area of people.apache.org to the
24 distribution directories on www.apache.org/dist/poi/ and
25 people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.poi/
26 - move the redirection pom from your area of people.apache.org to
27 people.apache.org/repo/m1-ibiblio-rsync-repository/poi/poms/
28 - copy the new distributions to archive.apache.org
29 - remove the old distributions from www.apache.org/dist/
30 - wait for the distributions to appear on your favourite mirror
32 - generate announcements
33 - generate www pages and upload
34 - bump release ID in build.xml
35 - send announcements to user and dev lists
36 - send announcements to announcement@apache.org, announcements@jakarta.apache.org
37 - news to newsgroups: comp.lang.java.softwaretools