From afa4e4a9db0482e965b5e28c9deeaa0c2a3708e2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Wed, 3 Apr 2019 16:23:43 +0200 Subject: [PATCH] docs: let's not close the milestone early --- docs/RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/RELEASE.md b/docs/RELEASE.md index 583d5d4d4a..0b1b230296 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -12,7 +12,7 @@ title: Steps to a Successful Release 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) +9. [After final release] 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`)