Update release.md

Author: bact

release.md

@@ -9,8 +9,9 @@ SPDX-License-Identifier: CC0-1.0
 0. Check if the package can be built properly.
    Include "[cd build]" in the commit message to trigger wheel building.
 1. Update `CHANGELOG.md` with a short summary of important changes since
-   the previous release. For example, deprecation or termination of support.
-2. This project follows [semantic versioning][semver].
+   the previous stable release.
+   For example, deprecation or termination of support.
+3. This project follows [semantic versioning][semver].
    Ensure the version and release date fields (if any) in these files
    have been updated to the version of the new planned release:
     - `codemeta.json`
@@ -21,20 +22,21 @@ SPDX-License-Identifier: CC0-1.0
     - `CITATION.cff`
     - `README.md`
     - `README.TH.md`
-3. Navigate to the [releases page][releases] and click the
+4. Navigate to the [releases page][releases] and click the
    "Draft a new release" button.
    Only project maintainers are able to perform this step.
-4. Then enter the new tag in the "Choose a tag" box.
+5. Then enter the new tag in the "Choose a tag" box.
    The tag should begin with "v", as in, for instance, `v5.0.1`.
-5. The release title should be the same as the new version tag.
+6. The release title should be the same as the new version tag.
    For instance, the title could be `v5.0.1`.
-6. Add a short summary of important changes in this release.
+7. Add a short summary of important changes since the previous stable
+   release.
    _This should be similar to what have been logged in `CHANGELOG.md`._
    Then click the "Generate release notes" button.
-7. You can optionally include any particular thank-you's to contributors or
+9. You can optionally include any particular thank-you's to contributors or
    reviewers in a note at the bottom of the release.
-8. You can then click "Publish release" button.
-9. If [the CI][ci] run is [successful][actions],
+10. You can then click "Publish release" button.
+11. If [the CI][ci] run is [successful][actions],
    then the release will be published on both
    the GitHub release page and also the [Python Package Index][pypi].