Page History

...

1. query dev@ for any open issues, it helps to look at JIRA first
2. create tag, create release branch
3. check out release branch
4. Set correct version in the pom files:
   • Linux:
     • find . -name "pom.xml" | xargs sed -i -e "s/1.4-SNAPSHOT/1.4-m1/g"
     • find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4-m1/g"
   • Mac OS X:
     • find . -name "pom.xml" | xargs sed -i "" -e "s/1.4-SNAPSHOT/1.4-m1/g"
     • find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.4-m1/g"
5. add JIRA generated release notes to CHANGELOG-1.4
6. commit to release branch
7. call release.sh (see note)
8. test the distribution (examples, rat, etc)
9. upload m2-repo and dist directory from target/ to p.a.o (see below)
10. upload commons/KEY into dist folder on p.a.o
11. send vote message
12. wait
13. upload to mirrors (see below)
14. release the version in JIRA
15. wait 24 hours for mirrors to pick them up
16. announce

NOTE: If you get an error while generating javadocs like the one that follows, run a "mvn clean install" followed by a "mvn javadoc:jar", then re-run release.sh.
Example of error: java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl

Releasing Apache Wicket 1.3.x

...

1. add the release to http://wicket.apache.org/quickstart.html and set it as default
2. upload the JavaDocs to the website at http://wicket.apache.org/docs/wicket-x.y.z/^{Image Removed} and point JavaDocs link to it

...