From bb980eed8af1c2a416daaa9a7ff4f89a279d5597 Mon Sep 17 00:00:00 2001 From: Steve Loeppky Date: Wed, 6 Jul 2022 12:51:02 -0700 Subject: [PATCH] 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 --- docs/RELEASE_ISSUE_TEMPLATE.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/RELEASE_ISSUE_TEMPLATE.md b/docs/RELEASE_ISSUE_TEMPLATE.md index 3f276f26305..224c784e795 100644 --- a/docs/RELEASE_ISSUE_TEMPLATE.md +++ b/docs/RELEASE_ISSUE_TEMPLATE.md @@ -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: