summaryrefslogtreecommitdiffstats
path: root/meson.version (follow)
Commit message (Collapse)AuthorAgeFilesLines
* meson: update version to 257~develLuca Boccassi2024-06-111-1/+1
|
* Finalize NEWS and version for v256v256Luca Boccassi2024-06-111-1/+1
|
* Update version and finalize NEWS for 256~rc4v256-rc4Luca Boccassi2024-06-061-1/+1
|
* meson: set version to 256~rc3Luca Boccassi2024-05-221-1/+1
|
* Finalize for v256~rc2v256-rc2Luca Boccassi2024-05-151-1/+1
|
* meson: update version numbers for 256~rc1Luca Boccassi2024-04-251-1/+1
|
* meson: Start adding devel and rc suffixes to the project versionDaan De Meyer2024-02-141-0/+1
Let's make sure that versions generated by meson-vcs-tag.sh always sort higher than official and stable releases. We achieve this by immediately updating the meson version in meson.build after a new release. To make sure this version always sorts lower than future rcs, we suffix it with "~devel" which will sort lower than "~rcX". The new release workflow is to update the version in meson.build for each rc and the official release and to also update the version number after a new release to the next development version. The full version is exposed as PROJECT_VERSION_FULL and used where it makes sense over PROJECT_VERSION. We also switch to reading the version from a meson.version file in the repo instead of hardcoding it in meson.build. This makes it easier to access both inside and outside of the project. The meson-vcs-tag.sh script is rewritten to query the version from meson.version instead of passing it in via the command line. This makes it easier to use outside of systemd since users don't have to query the version themselves first.