Much of this information is internal documentation. Care has not been made to make links work and make the documentation conprehensible for outsiders.
Different versions of the tool are periodically built and released.
The released versions of the tool can be downloaded from the Download page for CPN Tools. The home page CPN Tools also contains a link to a page concerning http://cpntools.org/cpntools/releases.wiki CPN Tools Releases.
External releases are meant for all users. External releases should be thoroughly tested and very stable.
After building an external release the following must be done:
Update version number in text near top of page, e.g. “The latest externally released version of CPN Tools is version 1.1.0.”
Update version number in link from text “What is new in CPN Tools?”
Update version number in link from text “Known bugs and bugfixes since latest release”
Update version number in text “What's new … (or in release version …)”
Update version number in text “Known bugs … (or in release version …)”
Update version number in links from 2 texts ”(or in release…)”
Announce the release of a new version
Update the figure in /web/cpntools/public_html/bin/users.png
Log in to machine with access to license database
Update /web/cpntools/public_html/bin/releases.dat with a data point for the (approximate) release date of the
Run users.sh again
Consider whether tool descriptions should be updated in various tool databases. Probably only necessary with major changes, e.g. availability on new platform or new analysis tool.
Internal releases are primarily meant to be used within the CPN group. Internal releases may not be thoroughly tested. They generally contain a number bug fixes or feature enhancements that are particularly useful for users (who are not programmers) of the tool.
The internal releases are only visible when downloading from within DAIMI. Internal releases are indicated by the text “development” next to the version number, e.g.
CPN Tools 1.0.8 development
After building an internal release, an email should be sent to the
CPN Tools group (firstname.lastname@example.org) announcing the new internal version. If the internal release contains a bug fix that is particularly relevant for a user that is not a member of the CPN Tools group, then this user should also be notified.
Each internal and external release has a version number with the format
The major version number
X is incremented when major changes are made in the tool. The major version number is only incremented for a new external version after a decision has been made by people in the file:people management and work groups. When
X is incremented, the
Z values are initially set to 0.
Y values indicate whether a version is an internal or external version. Even numbers (0,2,4,…) are used for external versions, while odd numbers (1,3,5,…) are used for internal versions.
Y values are generally incremented when changing from internal to external versions. When the
Y value is incremented, the
Z value is initially set to 0.
Z values are incremented when small changes are made. When developing new features, internal versions are made fairly regularly, and the
Z value will be incremented each time a new internal version is made.
Z values are rarely incremented for an external release, and they will probably only be incremented if a new external release is made to fix a catastrophic bug (such as not being able to save or load models) in the most recent external release.