]> git.ipfire.org Git - thirdparty/systemd.git/blob - docs/RELEASE.md
docs: place all our markdown docs in rough categories
[thirdparty/systemd.git] / docs / RELEASE.md
1 ---
2 title: Steps to a Successful Release
3 category: Contributing
4 ---
5
6 # Steps to a Successful Release
7
8 1. Add all items to NEWS
9 2. Update the contributors list in NEWS (`ninja -C build git-contrib`)
10 3. Update the time and place in NEWS
11 4. Update version and library numbers in `meson.build`
12 5. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
13 6. Do `ninja -C build`
14 7. Make sure that the version string and package string match: `build/systemctl --version`
15 8. Upload the documentation: `ninja -C build doc-sync`
16 9. [After final release] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
17 10. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
18 11. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
19 12. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
20 13. [After final release] Also push commits to stable, create an empty -stable branch: `git push systemd-stable origin/master:master origin/master:refs/heads/${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).