RELEASE: mark a few items for the final step

Doesn't make much sense to push RCs to the stable repository, just
do that in the final tag push

diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index df04cb47ced97f21423a686a252285e2a66a506e..d98fe0a2f9cbee79d7976f87dd3f1c2a65d90982 100644 (file)
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -22,7 +22,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
 13. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
 14. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
 15. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released | Online resources https://systemd.io/`)
-16. Push commits to stable, create an empty -stable branch: `git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable`.
-17. Build and upload the documentation (on the -stable branch): `ninja -C build doc-sync`
+16. [FINAL] Push commits to stable, create an empty -stable branch: `git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable`.
+17. [FINAL] Build and upload the documentation (on the -stable branch): `ninja -C build doc-sync`
 18. [FINAL] Change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).
 19. [FINAL] Change the Github Pages branch in the stable repository to the newly created branch (https://github.com/systemd/systemd-stable/settings/pages) and set the 'Custom domain' to 'systemd.io'