Maintainer-Guidelines.md

@@ -96,15 +96,11 @@ The process is equal to the making of a release candidate, but without making an
 
 ### Publish to [GitHub Packages](https://github.com/orgs/metafacture/packages?repo_name=metafacture-core)
 
-1. Switch back to master (so in combination with the signed tag (see below) an SCM tag can be found and the proper named files are generated):
+1. Push your properly named branch to GitHub. Notice the `-rc` part of the branch's name:
     ```
-    git checkout master
+    git push origin A.B.C-rcN
     ```
-1. Make an annotated signed tag if you haven't done that yet:
-    ```
-    git tag -s metafacture-core-A.B.C-rcN
-    ```
-1. Push your properly named branch to GitHub. Notice the `-rc` part of the branch's name. Because there is `fetch --no-tags` in `actions/checkout@v2` the `-SNAPSHOT` suffix will always be appended (in comparison to doing `./gradlew publishAllPublicationsToGitHubPackagesRepository` locally, which will find the `SCM tag`). The publishing to GitHub packages is triggered then.
+ Because there is `fetch --no-tags` in `actions/checkout@v2` the `-SNAPSHOT` suffix will always be appended (in comparison to doing `./gradlew publishAllPublicationsToGitHubPackagesRepository` locally, which will find the `SCM tag`). The publishing to GitHub packages is triggered then.
 
 If we don't want `-SNAPSHOT` we may want to remove the `-SNAPSHOT` in `build.gradle`:
 ```
@@ -153,6 +149,11 @@ Note that `Packages` is not the same as [`Releases`](https://github.com/metafact
 
 a) It's going from your local Git repository to Sonatype to Maven Central. Each station requires some manual actions so you can double check that everything is ok. b) A release should also be published to GitHub.
 
+1. Switch to `master` branch. Merge the approved `rc` into master:
+   ```
+   git switch master; pull --no-ff origin A.B.C-rcN; git push origin master
+   ```
+
 1. Make sure you have a signed tag locally:
     ```
     git show metafacture-core-A.B.C