aboutsummaryrefslogtreecommitdiff
path: root/docs/sphinx/conf.py.in
diff options
context:
space:
mode:
authorAlex Merry <alex.merry@kde.org>2014-12-28 15:03:07 +0000
committerAlex Merry <alex.merry@kde.org>2015-01-24 14:45:33 +0000
commit959c374c022394a116e8ceb2b1fce2df11752068 (patch)
tree2f743ea16d9982c41f5328c83d11802882213913 /docs/sphinx/conf.py.in
parentcf5ccc7d9eba368846fae043855d9b064dac786d (diff)
downloadextra-cmake-modules-959c374c022394a116e8ceb2b1fce2df11752068.tar.gz
extra-cmake-modules-959c374c022394a116e8ceb2b1fce2df11752068.tar.bz2
Add SameMajorVersionWithPreleases compat option to ecm_setup_version.
SameMajorVersionWithPreleases is intended implement the versioning scheme followed by many KDE projects: minor releases after some high number (eg: 90) are considered to be pre-releases of the next major version, and are not compatible with the current major version. This allows alpha and beta releases to be ordered correctly by version-number-aware software like package managers (an alpha of version 2 should have a higher number than any release of version 1, but less than version 2.0). So a request for version 2.1.0 of a piece of software should not be satisfied by 2.93.4, because that is actually a pre-release of version 3. On the other hand, a request for version 2.91.0 should be satisfied by version 3.1.0. Note that prereleases are not considered unless explicitly requested, so 2.93.4 will not satisfy requests for version 3 (or version 2) of a piece of software.
Diffstat (limited to 'docs/sphinx/conf.py.in')
0 files changed, 0 insertions, 0 deletions