|Index > Developers > Release Procedure|
Subversion commit over https Required
This is the most important thing and the easiest to get wrong. If you can not commit to the repo, the release will fail in the middle and you will have to rollback the changes by hand.
You must be able to commit using svn over https to do a release. Make sure your check out is over https
$ svn info
Also make sure you can commit to the https checkout. This requires that you have a password setup on Codehaus, which is not the default for new Codehaus accounts. Double check this by making an insignificant change to a file and cheking it in.
$ vi somefile
If you mess up and need to rollback simply, generate a diff from svn, apply the diff using patch and commit:
$ svn diff -r155:154 > my.diff
Performing the release
For the latest release (3.2), here is the command i used instead of the release:perform command which loops indefinitely:
Using scpexe in addition to "ssh -M" in another terminal works great and this work around the problem indicated at http://jira.codehaus.org/browse/WAGONSSH-54.