Posting a Release

There are two types of releases. Point releases are made as necessary and are distinguished by the third digit in the version number, as in x.y.1. BioSPICE releases are made for each version of BioSPICE and are distinguished by the first digit in the version number, as in 1.0.0.

Making a Point Release

  1. Announce to jigcell@cs.vt.edu that a point release is being made and give a cut off date and time for commiting to the release
  2. If the point release has a tracking bug make sure all of its dependencies have been resolved
  3. Check out a clean copy of the source code
  4. Edit www/index.html.template and enter today's date at the bottom for when this version was released
  5. Check in your change
  6. Run make distro to build the release
  7. Look at the generated www/index.html file and make sure it has today's date, the correct version number, and is an official release
  8. Try installing the release
  9. Run the Model Builder and make sure it starts
  10. Do the same for the Run Manager
  11. Do the same for the Comparator
  12. On jigcell.biol.vt.edu, move /var/www/jigcell to /var/www/jigcell.bak.
  13. Create the new directory /var/www/jigcell and unpack jigcell.tgz in /var/www/jigcell. Change to the directory /var/www and run the commands:
    1. chmod -R a+r jigcell/
    2. find jigcell/ -type d -exec chmod a+x \{\} \;
    3. chgrp -R www-users jigcell/
    4. chmod -R g+w jigcell/
  14. Make sure http://jigcell.biol.vt.edu/jigcell/ looks correct, then remove /var/www/jigcell.bak.
  15. Announce to jigcell@cs.vt.edu that a release has been made
  16. Edit jigcell/project/Version.java and increment the tertiary version number by one
  17. Check in your change
  18. Close the tracking bug for the point release

If there is a major problem with a point release, file a bug on the problem, send mail to jigcell@cs.vt.edu. Post a new point release when the bug is fixed.

Making a BioSPICE Release

  1. Announce to jigcell@cs.vt.edu that a BioSPICE release is being made and give a cut off date and time for commiting to the release
  2. If the BioSPICE release has a tracking bug make sure all of its dependencies have been resolved
  3. Check out a clean copy of the source code
  4. Edit jigcell/project/Version.java and increment the primary version number by one, set the secondary and tertiary numbers to zero
  5. Edit www/index.html.template and enter today's date at the bottom for when this version was released
  6. Check in your changes
  7. Run make distro to build the release
  8. Look at the generated www/index.html file and make sure it has today's date, the correct version number, and is an official release
  9. Try installing the release
  10. Run the Model Builder and perform its validation tests
  11. Do the same for the Run Manager tests
  12. Do the same for the Comparator tests
  13. If possible, give the installer to someone else and have them try it on another system
  14. On jigcell.biol.vt.edu, move /var/www/jigcell to /var/www/jigcell.bak.
  15. Create the new directory /var/www/jigcell and unpack jigcell.tgz in /var/www/jigcell. Change to the directory /var/www and run the commands:
    1. chmod -R a+r jigcell/
    2. find jigcell/ -type d -exec chmod a+x \{\} \;
    3. chgrp -R www-users jigcell/
    4. chmod -R g+w jigcell/
  16. Make sure http://jigcell.biol.vt.edu/jigcell/ looks correct, then remove /var/www/jigcell.bak.
  17. Announce to jigcell@cs.vt.edu that a release has been made
  18. Send a message to support@biospice.org announcing that a release has been made and ask them to send any replies to jigcell@cs.vt.edu
  19. Edit jigcell/project/Version.java and increment the tertiary version number by one
  20. Check in your change
  21. Close the tracking bug for the BioSPICE release

If there is a problem with a BioSPICE release, file a bug on the problem and send mail to jigcell@cs.vt.edu. When the bug is fixed, follow the steps above except treat the version number as if you were making a point release.