Skip to content

Commit

Permalink
Update RELEASE_ISSUE_TEMPLATE.md based on 0.14.0 release
Browse files Browse the repository at this point in the history
Changes based on the 0.14.0 release: #9032

Items from 0.13.1 should also be incorporated: #9095
  • Loading branch information
BigLep committed Jul 6, 2022
1 parent ab25bce commit bb980ee
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions docs/RELEASE_ISSUE_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,12 @@ For each RC published in each stage:
1. Build: https://github.com/ipfs/distributions#usage.
2. Pin the resulting release.
3. Make a PR against ipfs/distributions with the updated versions, including the new hash in the PR comment.
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.
- 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).
- Announce the RC:
- [ ] On Matrix (both #ipfs and #ipfs-dev)
- [ ]
- This will automatically post to IPFS Discord #ipfs-chatter
- Examples from the past: [0.14.0 - fill this in]()
- [ ] Pin the topic
- [ ] 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:
Expand Down

0 comments on commit bb980ee

Please sign in to comment.