Releasing a new version of Refine

NOTE: This won't be fully complete/accurate until we've done a release of OpenRefine from Github and updated the instructions with the necessary step-by-step.

When releasing a new version of Refine, the following steps should be followed:

1. Make sure the trunk is stable and nothing has broken since the previous version. We need developers to stabilize the trunk and some volunteers to try out trunk/ for a few days.
2. Change the version number in RefineServlet.java.
3. Compose the list of changes in the code and on the wiki.
4. Tag the release candidate in git e.g. 2.6-rc1
5. Build the release candidate kits using the shell script (not just Ant). This must be done on Linux or Mac currently and only Mac can build kits for all three platforms (Linux, Windows, Mac).: ./refine dist 2.6
6. Upload the kits to the kit distribution server (where?)
7. Announce the beta/release candidate for testing
8. Repeat build/release candidate/testing cycle, if necessary.
9. Tag the release in git. Build the distributions and upload them.
10. Update the releases.js file. This triggers the prompt to users to update their installations.

NOTE: During the transition to Github, the releases.js file on Google Code needs to be updated because that's the one that existing installations are looking at. Post 2.6 only Github needs to be updated.

1. Announce on the mailing list.