@cryptotaxi247 / kubo / commits / 9b7a31d28

refactor: remove unnecessary tasks in RELEASE_ISSUE_TEMPLATE.md

galargh committed Mar 6, 2023 at 20:27 UTC 9b7a31d28847e317b4d8baa5ed3c7a5f55666f7b
1 file changed -16
docs/RELEASE_ISSUE_TEMPLATE.md
-16
@@ -13,7 +13,6 @@
13 * Expected RC date: week of YYYY-MM-DD
14 * 🚢 Expected final release date: YYYY-MM-DD
15 * Accompanying PR for improving the release process: (example: https://github.com/ipfs/kubo/pull/9391)
16 -* Accompanying Issue for updating the infra: (example: https://github.com/protocol/bifrost-infra/issues/2221)
16
17 See the [Kubo release process](https://pl-strflt.notion.site/Kubo-Release-Process-5a5d066264704009a28a79cff93062c4) for more info.
18
@@ -29,8 +28,6 @@ As usual, this release includes important fixes, some of which may be critical f
28
29 ### Required
30
32 -- [ ] Do we need to make any changes to the [infrastructure configuration](https://github.com/protocol/bifrost-infra/tree/master/ansible/inventories/bifrost/group_vars)?
33 -
31 ### Nice to have
32
33 ## 🔦 Highlights
@@ -60,8 +57,6 @@ This section covers tasks to be done ahead of the release.
57 - [ ] [GPG signature](https://docs.github.com/en/authentication/managing-commit-signature-verification) configured in local git and in GitHub
58 - [ ] [admin access to IPFS Discourse](https://discuss.ipfs.tech/g/admins)
59 - ask the previous release owner (or @2color) for an invite
63 - - [ ] [access to #bifrost](https://filecoinproject.slack.com/archives/C03MMMF606T) channel in FIL Slack
64 - - ask the previous release owner for an invite
60 - [ ] ![](https://img.shields.io/badge/not-PATCH-yellow?style=flat-square) [access to #shared-pl-marketing-requests](https://filecoinproject.slack.com/archives/C018EJ8LWH1) channel in FIL Slack
61 - ask the previous release owner for an invite
62 - [ ] [access to IPFS network metrics](https://github.com/protocol/pldw/blob/624f47cf4ec14ad2cec6adf601a9f7b203ef770d/docs/sources/ipfs.md#ipfs-network-metrics) dashboards in Grafana
@@ -79,11 +74,6 @@ This section covers tasks to be done ahead of the release.
74 - [example](https://github.com/ipfs/distributions/pull/756)
75 - [ ] ![](https://img.shields.io/badge/not-PATCH-yellow?style=flat-square) [ipfs/ipfs-docs](https://github.com/ipfs/ipfs-docs)
76 - [example](https://github.com/ipfs/ipfs-docs/pull/1298)
82 -- [ ] Notify the bifrost team about the upcoming release (_only if it is not the day of the release yet_) <details><summary>using `kuboreleaser release --version vX.Y.Z(-rcN) notify-bifrost --date YYYY-MM-DD` or ...</summary>
83 - - [ ] open an issue against [bifrost-infra](https://github.com/protocol/bifrost-infra)
84 - - [example](https://github.com/protocol/bifrost-infra/issues/2221)
85 - </details>
86 -- [ ] Link the [bifrost-infra](https://github.com/protocol/bifrost-infra) issue in the [Meta](#meta) section
77 - [ ] Verify there is nothing [left for release](-what-s-left-for-release)
78 - [ ] Create a release process improvement PR
79 - [ ] update the [release issue template](docs/RELEASE_ISSUE_TEMPLATE.md) as you go
@@ -151,9 +141,6 @@ This section covers tasks to be done during each release.
141 - [ ] wait for the [sync-release-assets](https://github.com/ipfs/kubo/actions/workflows/sync-release-assets.yml) workflow run to finish
142 - [ ] verify the release assets are present in the [GitHub release](https://github.com/ipfs/kubo/releases/tag/vX.Y.Z(-RCN))
143 </details>
154 -- [ ] Notify the bifrost team about the release <details><summary>using `kuboreleaser release --version vX.Y.Z(-rcN) notify-bifrost --date YYYY-MM-DD` or ...</summary>
155 - - [ ] create an issue comment on the issue in the [bifrost-infra](https://github/com/protocol/bifrost-infra)
156 - </details>
144 - [ ] Promote the release <details><summary>using `kuboreleaser release --version vX.Y.Z(-rcN) promote` or ...</summary>
145 - [ ] create an [IPFS Discourse](https://discuss.ipfs.tech) topic
146 - [prerelease example](https://discuss.ipfs.tech/t/kubo-v0-16-0-rc1-release-candidate-is-out/15248)
@@ -206,9 +193,6 @@ This section covers tasks to be done during each release.
193 - [ ] ![](https://img.shields.io/badge/only-FINAL-green?style=flat-square) merge the PR
194 - [ ] ![](https://img.shields.io/badge/only-FINAL-green?style=flat-square) verify the blog entry was published
195 </details>
209 -- [ ] ![](https://img.shields.io/badge/only-RC-blue?style=flat-square) Keep checking the [metrics](https://protocollabs.grafana.net/d/8zlhkKTZk/gateway-slis-precomputed?orgId=1) until the release issue is closed
210 - - [release notes](https://www.notion.so/pl-strflt/Kubo-Gateway-Release-Notes-6e0efff28ee540be9ccb8f2b85104c42)
211 - - post in the [#bifrost](https://filecoinproject.slack.com/archives/C018EJ8LWH1) channel in FIL Slack if there is a problem
196 - [ ] ![](https://img.shields.io/badge/only-FINAL-green?style=flat-square) Merge the [release](https://github.com/ipfs/kubo/tree/release) branch back into [master](https://github.com/ipfs/kubo/tree/master), ignoring the changes to [version.go](version.go) (keep the `-dev`) version, <details><summary>using `kuboreleaser release --version vX.Y.Z(-rcN) merge-branch` or ...</summary>
197 - [ ] create a new branch `merge-release-vX.Y.Z` from `release`
198 - [ ] create and merge a PR from `merge-release-vX.Y.Z` to `master`