mirror of
https://github.com/systemd/systemd
synced 2024-09-06 16:56:43 +00:00
![Daan De Meyer](/assets/img/avatar_default.png)
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.
2.6 KiB
2.6 KiB
title | category | layout | SPDX-License-Identifier |
---|---|---|---|
Steps to a Successful Release | Contributing | default | LGPL-2.1-or-later |
Steps to a Successful Release
- Add all items to NEWS
- Update the contributors list in NEWS (
ninja -C build git-contrib
) - Update the time and place in NEWS
- Update hwdb (
ninja -C build update-hwdb
,ninja -C build update-hwdb-autosuspend
, commit separately). - Update syscall numbers (
ninja -C build update-syscall-tables update-syscall-header
). - [RC1] Update library numbers in
meson.build
- Update version number in
meson.version
(e.g. fromv256~devel
tov256~rc1
or fromv256~rc3
tov256
) - Check dbus docs with
ninja -C build update-dbus-docs
- Update translation strings (
cd build
,meson compile systemd-pot
,meson compile systemd-update-po
) - drop the header comments fromsystemd.pot
+ re-add SPDX before committing. If the only change in a file is the 'POT-Creation-Date' field, then ignore that file. - 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 wantv255~rc1
to sort lower thanv255
. - Do
ninja -C build
- Make sure that the version string and package string match:
build/systemctl --version
- [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
- "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
- Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
- Update IRC topic (
/msg chanserv TOPIC #systemd Version NNN released | Online resources https://systemd.io/
) - [FINAL] Push commits to stable, create an empty -stable branch:
git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable
. - [FINAL] Build and upload the documentation (on the -stable branch):
ninja -C build doc-sync
- [FINAL] Change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).
- [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'
- [FINAL] Update version number in
meson.version
to the devel version of the next release (e.g. fromv256
tov257~devel
)