system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-09-06 16:56:43 +00:00
Code Issues Packages Projects Releases Wiki Activity
systemd/docs/RELEASE.md
Daan De Meyer ea2a57bee3 meson: Start adding devel and rc suffixes to the project version 
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.
2024-02-14 15:36:34 +01:00

2.6 KiB
Raw Blame History

title category layout SPDX-License-Identifier
Steps to a Successful Release Contributing default LGPL-2.1-or-later

Steps to a Successful Release

  1. Add all items to NEWS
  2. Update the contributors list in NEWS (ninja -C build git-contrib)
  3. Update the time and place in NEWS
  4. Update hwdb (ninja -C build update-hwdb, ninja -C build update-hwdb-autosuspend, commit separately).
  5. Update syscall numbers (ninja -C build update-syscall-tables update-syscall-header).
  6. [RC1] Update library numbers in meson.build
  7. Update version number in meson.version (e.g. from v256~devel to v256~rc1 or from v256~rc3 to v256)
  8. Check dbus docs with ninja -C build update-dbus-docs
  9. Update translation strings (cd build, meson compile systemd-pot, meson compile systemd-update-po) - drop the header comments from systemd.pot + re-add SPDX before committing. If the only change in a file is the 'POT-Creation-Date' field, then ignore that file.
  10. Tag the release: version=vXXX~rcY && git tag -s "${version}" -m "systemd ${version}". Note that this uses a tilde (~) instead of a hyphen (-) because tildes sort lower in version comparisons according to the version format specification, and we want v255~rc1 to sort lower than v255.
  11. Do ninja -C build
  12. Make sure that the version string and package string match: build/systemctl --version
  13. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
  14. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
  15. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
  16. Update IRC topic (/msg chanserv TOPIC #systemd Version NNN released | Online resources https://systemd.io/)
  17. [FINAL] Push commits to stable, create an empty -stable branch: git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable.
  18. [FINAL] Build and upload the documentation (on the -stable branch): ninja -C build doc-sync
  19. [FINAL] Change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).
  20. [FINAL] Change the Github Pages branch in the stable repository to the newly created branch (https://github.com/systemd/systemd-stable/settings/pages) and set the 'Custom domain' to 'systemd.io'
  21. [FINAL] Update version number in meson.version to the devel version of the next release (e.g. from v256 to v257~devel)