This is just how this team does releases, personally I'm a fan of only adding new features with minor version bumps, but it just depends on how the team releases and versions their software. Note: Occasionally new features are added in patch releases, this is especially common while the release is the latest minor version, but becomes less so after moving to a new minor version.
Sometimes bug patches occur for minor releases, in which case a separate number is incremented (patch version, like 3.14.7 which released after 3.15), this is often to fix problems for folks stuck on older versions for one reason or another. It tends to be with version numbers that new features and policies are added each minor version, and maybe that some old functions are removed.
You can get approximate release dates from the git repo: In the CMake documentation it looks like the screenshot. See one of the commits from Nikita Nemkin, more are linked in the issue above. This happened to hundreds of places in the CMake documentation. The HINTS are a list of directories where the install directory of deal.II is likely to be found. CMake 3.19.0, 3.19.1, and the upcoming 3.20.0 got added the CMake version when a feature was introduced. The version numbers are just decimal numbers, so 1 < 10, thus minor version 1 is an earlier release than minor version 10. In this case requiring at least version 9.0.0. A semi-updated version of cmake is available through yum, but named cmake3. To verify, check the version of CMake with the help of command provided below.
#Cmake versions how to#
3.2 is < 3.20, they are certainly not the same version. git -version git version 1.8.3.1 cmake -version cmake version 2.8.12.2 This gist is mainly because I always forget how to do it when setting up a new system for myself, but it also shows a simple method for dealing with alternative versions of software. CMake is not a build system but it generates build files for another.
0 kommentar(er)
