]>
Commit | Line | Data |
---|---|---|
1 | --- | |
2 | title: Steps to a Successful Release | |
3 | --- | |
4 | ||
5 | # Steps to a Successful Release | |
6 | ||
7 | 1. Add all items to NEWS | |
8 | 2. Update the contributors list in NEWS (`ninja -C build git-contrib`) | |
9 | 3. Update the time and place in NEWS | |
10 | 4. Update version and library numbers in `meson.build` | |
11 | 5. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"` | |
12 | 6. Do `ninja -C build` | |
13 | 7. Make sure that the version string and package string match: `build/systemctl --version` | |
14 | 8. Upload the documentation: `ninja -C build doc-sync` | |
15 | 9. [After final release] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones) | |
16 | 10. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate. | |
17 | 11. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically. | |
18 | 12. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`) | |
19 | 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). |