MakingANewRelease

Process to follow on making a new release of JIDT

Introduction

This page, intended for developers, outlines the process we follow in making a new release of JIDT:

1. Check the PDFs for all Demos in the repository are up to date
2. Update build.xml for the new version number
3. Update readme.txt with release notes etc
4. Build the releases in a clean svn download
5. Check sha1 of the new release: sha1sum infodynamics-dist-1.0.zip
6. Post the code to lizier.me, make new counter files, ready and chmod them via ssh access. (Can also chmod via a web ftp on siteground; but by copying old counter files they tend to have the right permissions already)
7. Post the Javadocs to lizier.me and link from our Documentation page
8. Link to the new code on the Downloads page, Installation page and the front page of the google code site
9. Update the news on the front page about the release and with release notes
10. Mail the mailing list
11. Tweet about the new release
12. Update jar to clojars