extra-cmake-modules.git/modules/BasicConfigVersion-SameMajorVersionWithPrereleases.cmake.in, branch v5.34.0-rc2 hurd extra-cmake-modules.git Revert "Add SameMajorVersionWithPreleases compat option to ecm_setup_version." 2015-01-24T14:47:59+00:00 Alex Merry alex.merry@kde.org 2015-01-24T14:47:59+00:00 d609e598170064b4ee65392177a9d07f4302698d This reverts commit 959c374c022394a116e8ceb2b1fce2df11752068. I merged and pushed the wrong branch. 
This reverts commit 959c374c022394a116e8ceb2b1fce2df11752068.

I merged and pushed the wrong branch.
Add SameMajorVersionWithPreleases compat option to ecm_setup_version. 2015-01-24T14:45:33+00:00 Alex Merry alex.merry@kde.org 2014-12-28T15:03:07+00:00 959c374c022394a116e8ceb2b1fce2df11752068 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. 
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.