docs: let's not close the milestone early

diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index 583d5d4d4a0e1efe31f854abbc92e504bd6c5ff8..0b1b230296d2431d5b9475f1926807f443e98391 100644 (file)
--- 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`)