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 version and library numbers in
meson.build
- 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 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.
- Tag the release:
version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"
- 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/
)
- Push commits to stable, create an empty -stable branch:
git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable
.
- 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’