Skip to content

Commit bb980ee

Browse files
authored
Update RELEASE_ISSUE_TEMPLATE.md based on 0.14.0 release
Changes based on the 0.14.0 release: #9032 Items from 0.13.1 should also be incorporated: #9095
1 parent ab25bce commit bb980ee

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/RELEASE_ISSUE_TEMPLATE.md

+5-3
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,12 @@ For each RC published in each stage:
2828
1. Build: https://github.com/ipfs/distributions#usage.
2929
2. Pin the resulting release.
3030
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).
3332
- 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
3537
- [ ] 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))
3638

3739
Checklist:

0 commit comments

Comments
 (0)