@cryptotaxi247 / kubo / commits / 4b50e5976

docs: move publishing npm package

galargh committed Sep 27, 2022 at 17:18 UTC 4b50e5976250f304208b95348eddc7390dfc8a48
1 file changed +20 -19
docs/RELEASE_ISSUE_TEMPLATE.md
+20 -19
@@ -78,6 +78,7 @@ Checklist:
78 - [ ] Wait for PR to build artifacts and generate diff (~30min)
79 - [ ] Inspect results, merge if CI is green and the diff looks ok
80 - [ ] Wait for `master` branch to build. It will automatically update DNSLink at https://dist.ipfs.tech (~30min)
81 + - [ ] Publish the RC to [the NPM package](https://www.npmjs.com/package/go-ipfs?activeTab=versions) by running https://github.com/ipfs/npm-go-ipfs/actions/workflows/main.yml (it happens automatically but it is safe to speed up the process and kick of a run manually)
82 - [ ] Cut a pre-release on [GitHub](https://github.com/ipfs/kubo/releases) ([instructions](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release), [example](https://github.com/ipfs/kubo/releases/tag/v0.16.0-rc1))
83 - Use `vX.Y.Z-rcN` as the tag.
84 - Link to the release issue in the description.
@@ -98,25 +99,7 @@ Checklist:
99 - [ ] Matrix
100 - [ ] Mention [early testers](https://github.com/ipfs/go-ipfs/tree/master/docs/EARLY_TESTERS.md) in the comment under the release issue ([example](https://github.com/ipfs/kubo/issues/9237#issuecomment-1258072509)).
101 - [ ] **Stage 3 - Internal Testing**
101 - - [ ] Infrastructure Testing.
102 - - [ ] Open an issue against [bifrost-infra](https://github.com/protocol/bifrost-infra) ([example](https://github.com/protocol/bifrost-infra/issues/2109)).
103 - - Spell out all that we want updated - gateways, the bootstraper and the cluster/preload nodes
104 - - Mention @protocol/bifrost-team in the issue if you opened it prior to the release
105 - - [Optional] Reply under a message about the issue in the #bifrost channel on FIL Slack once the RC is out. Send the message to the channel.
106 - - [ ] Check [metrics](https://protocollabs.grafana.net/d/8zlhkKTZk/gateway-slis-precomputed?orgId=1) every day.
107 - - Compare the metrics trends week over week.
108 - - If there is an unexpected variation in the trend, message the #bifrost channel on FIL Slack and ask for help investigation the cause.
109 - - [ ] IPFS Application Testing.
110 - - [ ] [IPFS Desktop](https://github.com/ipfs-shipyard/ipfs-desktop)
111 - - [ ] Ensure the RC is published to [the NPM package](https://www.npmjs.com/package/go-ipfs?activeTab=versions) ([happens automatically, just wait for CI](https://github.com/ipfs/npm-go-ipfs/actions)), you can run https://github.com/ipfs/npm-go-ipfs/actions/workflows/main.yml to force release new version
112 - - [ ] Upgrade to the RC in [ipfs-desktop](https://github.com/ipfs-shipyard/ipfs-desktop) and push to a branch ([example](https://github.com/ipfs/ipfs-desktop/pull/1826/commits/b0a23db31ce942b46d95965ee6fe770fb24d6bde)), and open a draft PR to track through the final release ([example](https://github.com/ipfs/ipfs-desktop/pull/1826)), you have to check out the repo to update package-lock.json
113 - - [ ] Ensure CI tests pass, repeat for new RCs
114 - - [ ] [IPFS Companion](https://github.com/ipfs-shipyard/ipfs-companion)
115 - - Start kubo daemon of the version to release.
116 - - Start a fresh chromium or chrome instance using `chromium --user-data-dir=$(mktemp -d)` (macos `/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=$(mktemp -d)`)
117 - - Start a fresh firefox instance using `firefox --profile $(mktemp -d)` (macos `/Applications/Firefox.app/Contents/MacOS/firefox --profile $(mktemp -d)`)
118 - - Install IPFS Companion from [vendor-specific store](https://github.com/ipfs/ipfs-companion/#readme).
119 - - Check that the comunication between Kubo daemon and IPFS companion is working properly checking if the number of connected peers changes.
102 + - [ ] Library Testing.
103 - [ ] [interop](https://github.com/ipfs/interop)
104 - [ ] Clone the `ipfs/interop` repo locally.
105 - [ ] Create a new branch (`kubo-release-vX.Y.Z-rcn`) from `master`.
@@ -134,6 +117,24 @@ Checklist:
117 - [ ] [WebUI](https://github.com/ipfs-shipyard/ipfs-webui)
118 - [ ] Run [CI workflow](https://github.com/ipfs/ipfs-webui/actions/workflows/ci.yml) with `vX.Y.Z-rcN` for the `kubo-version` input.
119 - [ ] Ensure that CI is green.
120 + - [ ] Infrastructure Testing.
121 + - [ ] Open an issue against [bifrost-infra](https://github.com/protocol/bifrost-infra) ([example](https://github.com/protocol/bifrost-infra/issues/2109)).
122 + - Spell out all that we want updated - gateways, the bootstraper and the cluster/preload nodes
123 + - Mention @protocol/bifrost-team in the issue if you opened it prior to the release
124 + - [Optional] Reply under a message about the issue in the #bifrost channel on FIL Slack once the RC is out. Send the message to the channel.
125 + - [ ] Check [metrics](https://protocollabs.grafana.net/d/8zlhkKTZk/gateway-slis-precomputed?orgId=1) every day.
126 + - Compare the metrics trends week over week.
127 + - If there is an unexpected variation in the trend, message the #bifrost channel on FIL Slack and ask for help investigation the cause.
128 + - [ ] IPFS Application Testing.
129 + - [ ] [IPFS Desktop](https://github.com/ipfs-shipyard/ipfs-desktop)
130 + - [ ] Upgrade to the RC in [ipfs-desktop](https://github.com/ipfs-shipyard/ipfs-desktop) and push to a branch ([example](https://github.com/ipfs/ipfs-desktop/pull/1826/commits/b0a23db31ce942b46d95965ee6fe770fb24d6bde)), and open a draft PR to track through the final release ([example](https://github.com/ipfs/ipfs-desktop/pull/1826)), you have to check out the repo to update package-lock.json
131 + - [ ] Ensure CI tests pass
132 + - [ ] [IPFS Companion](https://github.com/ipfs-shipyard/ipfs-companion)
133 + - Start kubo daemon of the version to release.
134 + - Start a fresh chromium or chrome instance using `chromium --user-data-dir=$(mktemp -d)` (macos `/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=$(mktemp -d)`)
135 + - Start a fresh firefox instance using `firefox --profile $(mktemp -d)` (macos `/Applications/Firefox.app/Contents/MacOS/firefox --profile $(mktemp -d)`)
136 + - Install IPFS Companion from [vendor-specific store](https://github.com/ipfs/ipfs-companion/#readme).
137 + - Check that the comunication between Kubo daemon and IPFS companion is working properly checking if the number of connected peers changes.
138 - [ ] **Stage 4 - Community Prod Testing** - _ONLY FOR FINAL RELEASE_
139 - [ ] Add a link from release notes to Discuss post (like we did here: https://github.com/ipfs/kubo/releases/tag/v0.15.0 )
140 - [ ] Keep the release notes as trim as possible (removing some of the top headers, like we did here: https://github.com/ipfs/kubo/releases/tag/v0.15.0 )