Add more info after the release.

Author: adiroiban

.github/workflows/github-deploy.yml

@@ -3,10 +3,12 @@ on:
   push:
     branches:
       - trunk
-    # To simplify the release process, the publishing is triggred on any push tag.
+    # To simplify the release process, the publishing is triggered on tag.
     # We should make sure to only push tags for new releases.
     # If we start using tags for non-release purposes,
     # this needs to be updated.
+    #
+    # We need to explicitly configure an expression that matches anything.
     tags: [ "**" ]
   pull_request:
 

RELEASE.rst

@@ -10,12 +10,20 @@ To do a release, follow these steps:
 * Update the `Changelog.rst` file with the summary of the changes.
 * Commit the changes to GitHub and create a PR
 * Request the review from `twisted-contributors` team.
-* Once the PR is approved create a `git tag` based on the latest commit from
-  the PR.
-  The tag name should be the current version.
-* Push the tag to Github.
-  This will automatically trigger the build process for the wheels and will
-  publish them to PyPI
+* Once the PR is approved, create a new release via `GitHub Releases<https://github.com/twisted/twisted-iocpsupport/releases/new>`_.
+  The tag name should be the current version. Select to create a new tag.
+  Select the release branch as the target branch.
+  Copy/paste the release notes.
+* Publish the release.
+  This will automatically trigger that creation of a new that,
+  which in turn will trigger the build process for the wheels and will
+  publish them to PyPI.
+
+Using GitHub Releases is not required.
+You can also just create and push a new tag.
+It will still trigger the publish process.
+
+GitHub Release should just make it a bit easier to detect the release of this project.
 
 
 Implementation details