Updating release template based off some 0.10 learnings (#8491)

* Updating release template based off some 0.10 learnings

This addresses the easy items in #8248

* Further updates based on 2021-10-07 discussion.

* Added OrbitDB to early testers.

* Fixing early tester username references.

* Being clear about how to contact early testers.

docs/EARLY_TESTERS.md

@@ -22,7 +22,7 @@ We will ask early testers to participate at two points in the process:
 
 ## Who has signed up?
 
-- [ ] pacman.store ([@RubenKelevra](https://github.com/RubenKelevra))
+- [ ] pacman.store (@RubenKelevra)
 - [ ] Infura (@MichaelMure)
 - [ ] Textile (@sanderpick)
 - [ ] Pinata (@obo20)
@@ -31,6 +31,7 @@ We will ask early testers to participate at two points in the process:
 - [ ] Siderus (@koalalorenzo)
 - [ ] Charity Engine (@rytiss, @tristanolive)
 - [ ] Fission (@bmann)
+- [ ] OrbitDB (@tabcat)
 
 ## How to sign up?
 

docs/RELEASE_ISSUE_TEMPLATE.md

@@ -18,10 +18,6 @@ As usual, this release includes important fixes, some of which may be critical f
 
 < top highlights for this release notes >
 
-## Changelog
-
-< changelog generated by bin/mkreleaselog >
-
 ## ✅ Release Checklist
 
 For each RC published in each stage:
@@ -35,8 +31,8 @@ For each RC published in each stage:
   4. Ask the infra team to update the DNSLink record for dist.ipfs.io to point to the new distribution.
 - cut a pre-release on [github](https://github.com/ipfs/go-ipfs/releases) and upload the result of the ipfs/distributions build in the previous step.
 - Announce the RC:
-  - [ ] On IRC/Matrix (both #ipfs and #ipfs-dev)
-  - [ ] To the _early testers_ listed in [docs/EARLY_TESTERS.md](https://github.com/ipfs/go-ipfs/tree/master/docs/EARLY_TESTERS.md).
+  - [ ] On Matrix (both #ipfs and #ipfs-dev)
+  - [ ] To the _early testers_ listed in [docs/EARLY_TESTERS.md](https://github.com/ipfs/go-ipfs/tree/master/docs/EARLY_TESTERS.md).  Do this by copy/pasting their GitHub usernames and checkboxes as a comment so they get a GitHub notification.  ([example](https://github.com/ipfs/go-ipfs/issues/8176#issuecomment-909356394))
 
 Checklist:
 
@@ -54,8 +50,6 @@ Checklist:
 - [ ] **Stage 1 - Internal Testing**
   - [ ] CHANGELOG.md has been updated
     - use [`./bin/mkreleaselog`](https://github.com/ipfs/go-ipfs/tree/master/bin/mkreleaselog) to generate a nice starter list
-  - [ ] Network Testing:
-    - [ ] test lab things - TBD
   - [ ] Infrastructure Testing:
     - [ ] Deploy new version to a subset of Bootstrappers
     - [ ] Deploy new version to a subset of Gateways
@@ -67,24 +61,15 @@ Checklist:
       - [ ] Upgrade to the RC in [ipfs-desktop](https://github.com/ipfs-shipyard/ipfs-desktop) and push to a branch ([example](https://github.com/ipfs/ipfs-desktop/pull/1826/commits/b0a23db31ce942b46d95965ee6fe770fb24d6bde)), and open a draft PR to track through the final release ([example](https://github.com/ipfs/ipfs-desktop/pull/1826))
       - [ ] Ensure CI tests pass, repeat for new RCs
     - [ ] [IPFS Companion](https://github.com/ipfs-shipyard/ipfs-companion) - @lidel
-    - [ ] [NPM on IPFS](https://github.com/ipfs-shipyard/npm-on-ipfs) - @achingbrain
-- [ ] **Stage 2 - Community Dev Testing**
-  - [ ] Reach out to the IPFS _early testers_ listed in [docs/EARLY_TESTERS.md](https://github.com/ipfs/go-ipfs/tree/master/docs/EARLY_TESTERS.md) for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR.
-  - [ ] Reach out to on IRC for beta testers.
-  - [ ] Run tests available in the following repos with the latest beta (check when all tests pass):
-    - [ ] [orbit-db](https://github.com/orbitdb/orbit-db)
-- [ ] **Stage 3 - Community Prod Testing**
+- [ ] **Stage 2 - Community Prod Testing**
   - [ ] Documentation
     - [ ] Ensure that [CHANGELOG.md](https://github.com/ipfs/go-ipfs/tree/master/CHANGELOG.md) is up to date
     - [ ] Ensure that [README.md](https://github.com/ipfs/go-ipfs/tree/master/README.md)  is up to date
-    - [ ] Ensure that all the examples we have produced for go-ipfs run without problems
     - [ ] Update docs by merging the auto-created PR in https://github.com/ipfs/ipfs-docs/pulls (they are auto-created every 12 hours)
-  - [ ] Invite the IPFS [_early testers_](https://github.com/ipfs/go-ipfs/tree/master/docs/EARLY_TESTERS.md) to deploy the release to part of their production infrastructure.
   - [ ] Invite the wider community through (link to the release issue):
     - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements)
-    - [ ] Twitter
-    - [ ] IRC
-- [ ] **Stage 4 - Release**
+    - [ ] Matrix
+- [ ] **Stage 3 - Release**
   - [ ] Final preparation
     - [ ] Verify that version string in [`version.go`](https://github.com/ipfs/go-ipfs/tree/master/version.go) has been updated.
     - [ ] Merge `release-vX.Y.Z` into the `release` branch.
@@ -111,7 +96,24 @@ Checklist:
   - [ ] Make sure any last-minute changelog updates from the blog post make it back into the CHANGELOG.
   - [ ] Mark PR draft created for IPFS Desktop as ready for review.
 
-## ❤️ Contributors
+
+## ⁉️ Do you have questions?
+
+The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode, which is also [accessible through our Matrix bridge](https://riot.im/app/#/room/#freenode_#ipfs:matrix.org).
+
+## Release improvements for next time
+
+< Add any release improvements that were observed this cycle here so they can get incorporated into future releases. >
+
+## Items for a separate comment
+
+< Do these as a separate comment to avoid the main issue from getting too large and checkbox updates taking too long. >
+
+### Changelog
+
+< changelog generated by bin/mkreleaselog >
+
+### ❤️ Contributors
 
 < list generated by bin/mkreleaselog >
 
@@ -122,7 +124,3 @@ Would you like to contribute to the IPFS project and don't know how? Well, there
 - Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
 - Join the discussion at [discuss.ipfs.io](https://discuss.ipfs.io/) and help users finding their answers.
 - Join the [🚀 IPFS Core Implementations Weekly Sync 🛰](https://github.com/ipfs/team-mgmt/issues/992) and be part of the action!
-
-## ⁉️ Do you have questions?
-
-The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode, which is also [accessible through our Matrix bridge](https://riot.im/app/#/room/#freenode_#ipfs:matrix.org).