Releasing Apache Wicket 1.4.x
Building the release
- query dev@ for any open issues, it helps to look at JIRA first
- create tag, create release branch
- check out release branch
- 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"
- add JIRA generated release notes to CHANGELOG-1.4
- commit to release branch
- call release.sh (see note)
- test the distribution (examples, rat, etc)
- upload m2-repo and dist directory from target/ to p.a.o (see below)
- upload commons/KEY into dist folder on p.a.o
- send vote message
- wait
- upload to mirrors (see below)
- release the version in JIRA
- wait 24 hours for mirrors to pick them up
- 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
Building the release
- query dev@ for any open issues, it helps to look at JIRA first
- create tag, create release branch
- check out release branch
- Set correct version in the pom files:
- Linux:
- find . -name "pom.xml" | xargs sed -i -e "s/1.3-SNAPSHOT/1.3.2/g"
- find . -name "pom.xml" | xargs sed -i -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"
- Mac OS X:
- find . -name "pom.xml" | xargs sed -i "" -e "s/1.3-SNAPSHOT/1.3.2/g"
- find . -name "pom.xml" | xargs sed -i "" -e "s/wicket\/trunk/wicket\/releases\/wicket-1.3.3/g"
- add JIRA generated release notes to CHANGELOG-1.3
- commit to release branch
- call release.sh
- test the distribution (examples, rat, etc)
- upload m2-repo and dist directory from target/ to p.a.o
- upload commons/KEY into dist folder on p.a.o
- send vote message
- wait
- upload to mirrors (see below)
- release the version in JIRA
- wait 24 hours for mirrors to pick them up
- announce
Uploading to the mirror system
http://apache.org/dev/mirror-step-by-step.html
Uploading to maven repository
I haven't got any really good way to put them in the maven mirrors. The problem is that right now we override the meta xml files, so only the latest version is listed. If we really should do this perfect we would modify meta files like /org/apache/wicket/wicket/maven-metadata.xml and add the version to it (as well as create the hashes again).
But for now this is sufficient:
- cd into the directory you have the artifacts which has been voted on.
- cp -R m2-repo/org/apache/wicket/* /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket/
- chmod -R g+w * /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/wicket
Further reading: README under /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
Announce
- http://wicket.apache.org
- http://wicket.apache.org/getting-wicket.html
- http://wicket.apache.org/news.html
- http://cwiki.apache.org/confluence/display/WICKETxSITE/Navigation - edit the nav bar links to latest releases
- us...@wicket.apache.org, d...@wicket.apache.org, annou...@wicket.apache.org, annou...@apache.org
- Misc. websites like javalobby, serverside, onjava etc.
Additional tasks
- add the release to http://wicket.apache.org/quickstart.html and set it as default
- upload the JavaDocs to the website at http://wicket.apache.org/docs/wicket-x.y.z/ and point JavaDocs link to it
Releasing Apache Wicket 1.2.x
TBD...