docs: update release steps for meson

diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index 4bf5ab8dc174e08f833c680960812bffceb81ff7..583d5d4d4a0e1efe31f854abbc92e504bd6c5ff8 100644 (file)
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -5,12 +5,14 @@ title: Steps to a Successful Release
 # Steps to a Successful Release
 
 1. Add all items to NEWS
-2. Update the contributors list in NEWS ("make git-contrib")
+2. Update the contributors list in NEWS (`ninja -C build git-contrib`)
 3. Update the time and place in NEWS
-4. Update version in configure.ac and library numbers in Makefile.am
-5. Check that "make distcheck" works
-6. Tag the release ("make git-tag")
-7. Upload the documentation ("make doc-sync")
-8. Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
-9. Send announcement to systemd-devel, with a copy&paste from NEWS
-10. Update IRC topic ("/msg chanserv TOPIC #systemd Version NNN released")
+4. Update version and library numbers in `meson.build`
+5. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
+6. Do `ninja -C build`
+7. Make sure that the version string and package string match: `build/systemctl --version`
+8. Upload the documentation: `ninja -C build doc-sync`
+9. Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
+10. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
+11. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
+12. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)