Releasing

Prerequisites

• Maven 3
• Ant 1.8.2
• Subversion 1.6

Steps

0. Check the Release Notes (in org.projectusus.documentation/Release Notes). Complete them if required. Commit & push.
1. Determine the version number to release.
   You can look at the parent POM if you are unsure. If it says 0.7.3-SNAPSHOT the version number will most likely be 0.7.3.
2. Create and push a git tag for the version, name it vA.B.C (replace A.B.C with the real version number): git tag -a vA.B.C -m "tag vA.B.C"
3. In the repository root directory, execute mvn clean install.
   If some tests fail when run in Maven that work in Eclipse, blame Maven Tycho and run mvn clean install -DskipTests.
4. Change into org.projectusus.updatesite and execute ant merge.
5. Change into org.projectusus.updatesite/svn and execute svn status.
6. If everything looks good (i.e. plugins and features with the correct version number have been added), execute svn commit -m "Release A.B.C" (replace A.B.C with the real version number). (login: same as google account, password: see https://code.google.com/hosting/settings)
7. Decide which version number the next release should have.
   Normally, this is simply done by incrementing the last part of the version number by one.
8. Go back to org.projectusus.updatesite and run ant increment-versions -Dnew.version=A.B.D (replace A.B.D with the number of the next version you are going to work on).
9. Commit and push the changed files to git: git commit -a -m "Release A.B.C"; git push origin master
10. Celebrate!