diff options
author | Brad King <brad.king@kitware.com> | 2014-02-19 14:15:42 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2014-02-19 14:30:13 (GMT) |
commit | 7cbab178718de26575fe98144e7e388b2f6735a6 (patch) | |
tree | 98e1e191a8687646dae44bd508f9b6f02d097666 /CONTRIBUTING.rst | |
parent | 4bb80396e09882dcb8bc0feb10de88351eb55e68 (diff) | |
download | CMake-7cbab178718de26575fe98144e7e388b2f6735a6.zip CMake-7cbab178718de26575fe98144e7e388b2f6735a6.tar.gz CMake-7cbab178718de26575fe98144e7e388b2f6735a6.tar.bz2 |
Change version scheme to use only two components for feature levels
Historically CMake used three version components for the feature level.
We released new features while incrementing only the third version
component. Since commit v2.8.2~105^2~4 (New version scheme to support
branchy workflow, 2010-04-23) we used the fourth version component for
bug-fix releases and the development date:
<major>.<minor>.<patch>[.<tweak>][-rc<n>] = Release
<major>.<minor>.<patch>.<date>[-<id>] = Development
This solidified use of three components for the feature level, and was
necessary to continue releasing 2.x versions because:
* Some existing projects performed floating-point comparisons of
${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION} to 2.x numbers
so ``x`` could never be higher than 9.
* Version 2.9.<date> was used briefly in post-2.8.0 development in
CVS prior to the transition to Git, so using it in releases may
have caused confusion.
Now that we are moving to 3.x versions, these two restrictions go away.
Therefore we now change to use only two components for the feature
level and use the scheme:
<major>.<minor>.<patch>[-rc<n>] = Release
<major>.<minor>.<date>[-<id>] = Development
Diffstat (limited to 'CONTRIBUTING.rst')
0 files changed, 0 insertions, 0 deletions