Release Versioning

CMakePPLang uses semantic versioning, often shortened called “semver”, for release versioning. In short, each release is tagged with a version in the form: MAJOR.MINOR.PATCH. The MAJOR version is incremented when an incompatible API change is made, the MINOR version is incremented when new functionality is added but doesn’t break the API, and the PATCH version is incremented for bug fixes that also do not break the API.

Although CMakePPLang is built on top of CMake, CMakePPLang mostly relies on fairly fundamental features of the CMake language, so it is versioned independently of CMake. We consider the CMakePPLang API stable regardless of underlying changes to CMake, although changes to the CMakePPLang backend may be necessary to account for changes in CMake. That said, if CMake ever increments from version 3.x.x to 4.0.0 and completely overhauls the basics of the CMake language, then we may need to go to increment to 2.0.0.

See Pinning a CMakePPLang Version for more information about pinning a specific CMakePPLang version in case of bugs in the latest version.