Modernize the release procedure.

Author: sadiepowell

docs/release-procedure.md

@@ -8,7 +8,6 @@ title: Release Procedure
 Name       | Description
 ---------- | -------
 `BRANCH`   | The branch on which the release is happening.
-`PREVIOUS` | The previous release's version number or the previous branch if the release is the first on that branch.
 `UPSTREAM` | The Git remote for the main InspIRCd repository.
 `VERSION`  | The new release's version number.
 
@@ -19,18 +18,16 @@ Name       | Description
 0. Run `tools/mkheaders` to update the copyright headers.
 0. If ABI breakages have been made then update `MODULE_ABI` in `include/moduledefs.h`.
 0. Update the version in `src/version.sh`.
-0. Commit the changes to `include/moduledefs.h` and `src/version.sh`.
+0. Commit the changes to `include/moduledefs.h` and `src/version.sh` with the message `Release VERSION.`.
 0. Ensure that the branch tip builds with no warnings. Checking [GitHub Actions](https://github.com/inspircd/inspircd/actions) is helpful as it builds with `-Werror`.
 0. Tag the release with `git tag VERSION`.
 0. Run `git push UPSTREAM BRANCH` and `git push UPSTREAM VERSION`.
-0. Add a [GitHub release](https://github.com/inspircd/inspircd/tags) for the VERSION on tag.
-0. Generate a list of contributors for the news post using `git log --pretty='  - %aN' PREVIOUS...VERSION | sort -fu`
-0. Create a news post on the website using the list of contributors from the previous step.
-0. Mark the new news post as featured and unmark the old one.
-0. If the release is stable then update `misc.currentVersion` in the website config to VERSION.
+0. Add a [GitHub release](https://github.com/inspircd/inspircd/tags) for the VERSION tag.
 0. Update the change log on the documentation site.
-0. Run the [API documentation workflow](https://github.com/inspircd/api-docs/actions/workflows/build.yml).
 0. If the release fixes a security vulnerability then create an advisory on the documentation site.
+0. Create a news post on the website using the change log from the previous step.
+0. Mark the new news post as featured and unmark the previous one.
+0. Run the [API documentation workflow](https://github.com/inspircd/api-docs/actions/workflows/build.yml).
 0. Update `INSP_VERSION` in the [Docker container build script](https://github.com/inspircd/docker/blob/master/.github/workflows/build-container.yml).
 0. Update the topic in the InspIRCd IRC channels.
 0. Post a link to the news post on the [InspIRCd social media accounts](/support).