docs: drop manual rc PR warning step

it is not automated, yay

diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index bb698a06015f0c8abf3d0017992a0d428df1a733..68b5e417e931e22a67b25279855245ae20513044 100644 (file)
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -13,16 +13,14 @@ SPDX-License-Identifier: LGPL-2.1-or-later
 4. Update hwdb (`ninja -C build update-hwdb`, `ninja -C build update-hwdb-autosuspend`, commit separately).
 5. Update syscall numbers (`ninja -C build update-syscall-tables update-syscall-header`).
 6. [RC1] Update version and library numbers in `meson.build`
-7. [RC1] Rename `.github/pull_request_template.md.disabled` to `.github/pull_request_template.md` to display the warning about soft-freeze for new features
-8. [FINAL] Rename `.github/pull_request_template.md` to `.github/pull_request_template.md.disabled` to hide the warning about soft-freeze for new features
-9. Check dbus docs with `ninja -C build update-dbus-docs`
-10. Update translation strings (`cd build`, `meson compile systemd-pot`, `meson compile systemd-update-po`) - drop the header comments from `systemd.pot` + re-add SPDX before committing.
-11. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
-12. Do `ninja -C build`
-13. Make sure that the version string and package string match: `build/systemctl --version`
-14. Upload the documentation: `ninja -C build doc-sync`
-15. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
-16. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
-17. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
-18. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
-19. [FINAL] Push commits to stable, create an empty -stable branch: `git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).
+7. Check dbus docs with `ninja -C build update-dbus-docs`
+8. Update translation strings (`cd build`, `meson compile systemd-pot`, `meson compile systemd-update-po`) - drop the header comments from `systemd.pot` + re-add SPDX before committing.
+9. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
+10. Do `ninja -C build`
+11. Make sure that the version string and package string match: `build/systemctl --version`
+12. Upload the documentation: `ninja -C build doc-sync`
+13. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
+14. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
+15. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
+16. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
+17. [FINAL] Push commits to stable, create an empty -stable branch: `git push systemd-stable --atomic origin/main:main origin/main:refs/heads/${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).