Version Number Notes

Information for the general public

All official releases have a version number like x.y.z (Build n). The first number (x) in the version is incremented for each BioSPICE release. The second number (y) is the major release number for the JigCell project (i.e., the second number is only incremented when there are major changes in JigCell). The third number (z) is changed for every public release.

Unofficial releases are releases that are not available to the public. If you encounter a bug, one of the developers may send you an unofficial release so that you can confirm that the bug has been fixed. Unofficial releases have the form x.y.z-Note (Build n), where "Note" is a short piece of text.

Information for internal developers

Working with Version Numbers

The main version numbers are kept in jigcell/project/ This file contains a Java class that you are free to use whenever you need version information. To change the version numbers for the project, simply change this file.

Build Numbers

The "Build" or "Rebuild" numbers are actually the Subversion version numbers. This should allow developers to easily see the exact state of the code in any release. Whether the version number says "Build" or "Rebuild" tells you whether JigCell was built from a pristine (i.e., no local modifications) Subversion copy, or if it was built from some other source.

The build number and whether or not the release is official is stored in jigcell/project/ This file is automatically generated by the build system, so do not edit it or check it into the Subversion repository.

Unofficial Releases or Special Releases

If you need to give someone an unofficial release, you should create the SPECIAL file in the same directory as the Makefiles. In the SPECIAL file, type a short string that will help other people determine where the unofficial release originated; the string may contain only letters, numbers, underscores (_), and hyphens (-). A good suggestion is to just use your name followed by a 1 (and then increment the number each time you make a special release). For instance, George might type George1 in the SPECIAL file. Once you have created the SPECIAL file, the build system will automatically ensure that it is incorporated into