Creating a jGridstart release

When, after fixing bugs and adding new features, you'd like to bring those
changes to the general public, it is time to make a new release of jGridstart.
This would involve the following steps:

Make sure that everything works.
When you've made changes that might involve platform-specific behaviour,
make sure to test affected functionalities on the major platforms (Linux,
Mac OS X and Windows). Please see jgridstart-tests/README.md for more
information on that.

Update version numbers.
Consider what modules have changed. For those modules, update the version
number. Also update the version number where these are used as dependencies.

If you just changed jgridstart-main, you can run the following commands
(using xmlstarlet) to update the relevant modules to version x.y:

Create final version
by running mvn clean install from the project's root.

Sign resulting JAR
using a commercial code-signing certificate, so that users know they are
relatively safe running the code. This is important, since jGridstart
requires full access to the system and won't work without a signed JAR.
You can use jarsigner:

Then copy all files found in jgridstart-jws/target/jnlp to the location.

Publish javadoc.
TODO: This is something that still needs to be put in place.

Update the Wiki.http://jgridstart.nikhef.nl/Releases contains a list of jGridstart's
releases. Add a new entry, make sure the links point to the correct release
location; review source code history and add changes relevant for users and
CAs (with bug links when present).
Also update http://jgridstart.nikhef.nl/Test to point to the new release.

Commit and create tag so that the source code reflects the release as well.

git commit -m 'release x.y'
git tag jgridstart_x.y
git push --tags

Prepare for Certificate Authority. The DutchGrid CA uses jGridstart
directly, and we prepare the release for them a little more. Just run the
script copyrelease.sh x.y in jgridstart.nikhef.nl's /ca directory. Then
you're ready to mail them!

It would be nice to eventually use the Maven release plugin to automate a lot of this.
For now, stick to this and you're fine.
And finally: please feel free to update and improve this file!