]> git.ipfire.org Git - thirdparty/systemd.git/blame - docs/RELEASE.md
Merge pull request #16841 from keszybz/acl-util-bitmask
[thirdparty/systemd.git] / docs / RELEASE.md
CommitLineData
c3e270f4
FB
1---
2title: Steps to a Successful Release
4cdca0af 3category: Contributing
b41a3f66 4layout: default
c3e270f4
FB
5---
6
c1d3483d 7# Steps to a Successful Release
d11343ac
ZJS
8
91. Add all items to NEWS
f5a44d42 102. Update the contributors list in NEWS (`ninja -C build git-contrib`)
d11343ac 113. Update the time and place in NEWS
f5a44d42 124. Update version and library numbers in `meson.build`
3c682b17
ZJS
135. Check dbus docs with `ninja -C build man/update-dbus-docs`
146. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
157. Do `ninja -C build`
168. Make sure that the version string and package string match: `build/systemctl --version`
179. Upload the documentation: `ninja -C build doc-sync`
1810. [After final release] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
1911. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
2012. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
2113. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
2214. [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).