Merge pull request #1284 from tweag/ch/release-procedure-more-explicit

MAINTAINERS.md: make release procedure more explicit

Author: mergify[bot]

MAINTAINERS.md

@@ -26,20 +26,25 @@
     and push changes back to the release branch.
 - [ ] Verify that the final version of the release branch is green
 - [ ] Create release tag (`v<major>.<minor>`) on the release branch and
-  push
-- [ ] Go to the [release
-  page](https://github.com/tweag/rules_haskell/releases)
+  push it: `git push origin v<major>.<minor>`
+- [ ] Go to the [release page](https://github.com/tweag/rules_haskell/releases)
     - click on “Draft a new release”
     - name `v<major>.<minor>`
+    - select the tag you created in the previous item, it should be in
+      github's dropdown list
     - copy the changelog section into the description
+    - you don't need to provide the source `.zip` and `.tar.gz` archives,
+      github does it automatically.
     - release
 - [ ] Push `rules_haskell` version in start script to new release tag,
-  test it in a temporary directory, create PR against master
-  - [ ] Publish start script and website by merging the commit into
-        the `release` branch.
+      test it in a temporary directory, create PR against master
+  - [ ] Once PR has been merged, publish start script and website
+        by checkouting the `release` branch and merging master into it.
+        Then push the `release` branch, to trigger deployment.
   - [ ] Check whether https://haskell.build/start has the newest start
         script (netlify has problems sometimes).
-- [ ] Announce the new version (on Twitter)
+- [ ] Announce the new version (on Twitter) by asking someone with Twitter
+      rights.
 
 ### Remove these PRs from minor releases