Update RELEASE_ISSUE_TEMPLATE.md based on 0.14.0 release
Changes based on the 0.14.0 release: https://github.com/ipfs/kubo/issues/9032 Items from 0.13.1 should also be incorporated: https://github.com/ipfs/kubo/pull/9095
Steve Loeppky committed
Jul 6, 2022 at 12:51 UTC
bb980eed8af1c2a416daaa9a7ff4f89a279d5597
1 file changed
+5
-3
docs/RELEASE_ISSUE_TEMPLATE.md
+5
-3
@@ -28,10 +28,12 @@ For each RC published in each stage:
28
1. Build: https://github.com/ipfs/distributions#usage.
29
2. Pin the resulting release.
30
3. Make a PR against ipfs/distributions with the updated versions, including the new hash in the PR comment.
31
- 4. Ask the infra team to update the DNSLink record for dist.ipfs.io to point to the new distribution.
32
-- 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.
31
+ - Note the DNSLink record for dist.ipfs.io points to the new distribution as part of [CI after merging into master](https://github.com/ipfs/distributions/blob/master/.github/workflows/main.yml#L154).
32
- Announce the RC:
34
- - [ ] On Matrix (both #ipfs and #ipfs-dev)
33
+ - [ ]
34
+ - This will automatically post to IPFS Discord #ipfs-chatter
35
+ - Examples from the past: [0.14.0 - fill this in]()
36
+ - [ ] Pin the topic
37
- [ ] 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))
38
39
Checklist: