]> git.ipfire.org Git - thirdparty/systemd.git/blame - docs/RELEASE.md
fs-util: no need for fchmod_and_chown() to access /proc/self/fd directly
[thirdparty/systemd.git] / docs / RELEASE.md
CommitLineData
c3e270f4
FB
1---
2title: Steps to a Successful Release
3---
4
c1d3483d 5# Steps to a Successful Release
d11343ac
ZJS
6
71. Add all items to NEWS
f5a44d42 82. Update the contributors list in NEWS (`ninja -C build git-contrib`)
d11343ac 93. Update the time and place in NEWS
f5a44d42
ZJS
104. Update version and library numbers in `meson.build`
115. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
126. Do `ninja -C build`
137. Make sure that the version string and package string match: `build/systemctl --version`
148. Upload the documentation: `ninja -C build doc-sync`
afa4e4a9 159. [After final release] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
f5a44d42
ZJS
1610. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
1711. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
1812. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
3be49391 1913. [After final release] Also push commits to stable, create an empty -stable branch: `git push systemd-stable origin/master:master origin/master:v${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).