Difference between revisions of "Documentation/4.1/Developers/Versioning"
From Slicer Wiki
m |
m |
||
| Line 3: | Line 3: | ||
{{ambox|text=This page describe the Slicer versioning scheme for packages}} | {{ambox|text=This page describe the Slicer versioning scheme for packages}} | ||
| − | = Package naming scheme = | + | = Slicer Package naming scheme = |
<pre>Slicer-<MAJOR_VERSION>.<MINOR_VERSION>.<PATCH_VERSION>-<TWEAK_VERSION>[-rc{1|2|3...}][-<DATE>][-svn<REV>][-dirty]-<ARCH>-<PLATFORM></pre> | <pre>Slicer-<MAJOR_VERSION>.<MINOR_VERSION>.<PATCH_VERSION>-<TWEAK_VERSION>[-rc{1|2|3...}][-<DATE>][-svn<REV>][-dirty]-<ARCH>-<PLATFORM></pre> | ||
| Line 19: | Line 19: | ||
: The '''-dirty''' prefix indicates if the package has been generated from a locally modified source tree. | : The '''-dirty''' prefix indicates if the package has been generated from a locally modified source tree. | ||
| − | + | == Example of linux 64bits packages == | |
[ File name ][ date ][ build type ][ note ] | [ File name ][ date ][ build type ][ note ] | ||
Slicer-4.0.0-linux-amd64 2011-11-24 release release of Slicer 4.0.0 | Slicer-4.0.0-linux-amd64 2011-11-24 release release of Slicer 4.0.0 | ||
Revision as of 20:56, 7 January 2012
Home < Documentation < 4.1 < Developers < Versioning |
This page describe the Slicer versioning scheme for packages |
Slicer Package naming scheme
Slicer-<MAJOR_VERSION>.<MINOR_VERSION>.<PATCH_VERSION>-<TWEAK_VERSION>[-rc{1|2|3...}][-<DATE>][-svn<REV>][-dirty]-<ARCH>-<PLATFORM>
There are 2 types of builds, releases and developments:
- Release
- Special builds made on a given revision (e.g. r19033: "ENH: Slicer 4.0.1")
- Don't contain date or revision number.
- The optional suffix -rc{1|2|3|...} identifies the release candidates leading to a final release.
- Eventually, a tweak number can be added (e.g. 4.0.1-1)
- Development
- Nightly or experimental builds
- Contains suffixes after the major.minor.patch version
- The suffix svn<REV> allows to identify the revision associated with the current package.
- The -dirty prefix indicates if the package has been generated from a locally modified source tree.
Example of linux 64bits packages
[ File name ][ date ][ build type ][ note ] Slicer-4.0.0-linux-amd64 2011-11-24 release release of Slicer 4.0.0 Slicer-4.0.0-2011-12-10-linux-amd64 2011-11-25 development nightly build after 4.0.0 Slicer-4.0.1-rc1-linux-amd64 2012-01-04 release release candidate 1 of Slicer 4.0.1 Slicer-4.0.1-rc1-2012-01-05-linux-amd64 2012-01-05 development nightly build after the release candidate Slicer-4.0.1-rc2-linux-amd64 2012-01-11 release release candidate 2 of Slicer 4.0.1 Slicer-4.0.1-rc2-2012-01-12-linux-amd64 2012-01-12 development nightly build after the release candidate Slicer-4.0.1-linux-amd64 2012-01-14 release release of Slicer 4.0.1 Slicer-4.0.1-2012-01-20-linux-amd64 2012-01-20 development nightly build after 4.0.1 Slicer-4.0.1-1-linux-amd64 2012-01-28 release tweak version 1 of Slicer 4.0.1 Slicer-4.0.2-linux.amd64 2012-06-05 release release of Slicer 4.0.2
