20:th December 2007
There are four different kind of releases three stable releases and one relase as a snapshot from the source base.
- Release of SAVE-IDE V0.5
14:th December 2007
- Snapshot: SAVE-IDE V0.5.1.20071214. Each plug-in have its own version number. The qualifier is the same as the SAVE-IDE's release qualifier.
- Tagged pre-release: This is the first release of SAVE-IDE and will be released as a alpha-version. For this release no tagged version for bug fixes will be crated.
1:th December 2007
- Tagged freezed version: /tags/pre-release0.5.0alpha20071201/. Observe that this version is considered to be freezed, in other words no commits are allowed. The purpose of the tagged version is to have a base version to test bug fixes againt if the current main code line is broken or the bug fix do not run with the main code line.
(1) Stable release with major changes
(2) Stable release with minor changes
(3) Stable release based on builds and/or bug fixes
(4) Unstable release based on a snaphot of the source base or a bug fix for a single bug report
Each release follows a release plan made by the release manager, project administrator and/or the SAVE-IDE core group. Also the releases are marked with a version number according to the scheme that follows.
This guideline for version numbering is valid for plug-ins that can be built based on the source base for SAVE-IDE. Other plug-ins or source bases built to be a part of the SAVE_IDE should follow the version numbering for SAVE-IDE. The version number will be constructed as 'major.minor.micro.revision_qualifier', e.g., a packege named save-ide_220.127.116.11_200712131450'.
When following this guide 'major.minor' version number should be used for official external releases and 'major.minor.micro.revision_qualifier' version number should be used for internal releases.
When new functionality is added and/or significant improvements and corrections have been made the SAVE-IDE is released witn an increase of the major version number. The major number is also increeased when new milestones are reached with a set of successful bug fixes.
Example, assume that
The minor version number is increased when several new functionalities is implemented and tha plan is to release them as a package with an increase of the major version number. The minor number can also be increased if bugs are fixed that are severe for the usability of SAVE-IDE.
SAVE-IDE 1.6 is a current version, and a new editor is implemented for a new way of editing behavioural models then the next release will be increased to
Example, on the way to release a new graphical editor some tools are implemented. These tools is useful even without the editor. In such case a new release can be packaged and the current version
The micro version number is increased when building after bug fixes and maintenance the code is considered to be stable. This micro number is preferably used for the individual plug-ins, and when the plug-in or package not are put up at any download site.
The revision version number is used for releases that are unstable. Since this number also include builds that not are initiated by bug fix or implementation this part includes a qualifier consisting of the date and time for the build. This is useful when there is a need to test the implementation without any intervening bug fixes.
SAVE-IDE 1.6 can be increased to
Example, for builds between bug fixes or implementation of new functionality tracability is dicated by the qualifier. An automated build where done at a pre-determined time this build will get a version number as