I copied release checklist from https://raw.githubusercontent.com/ipfs/kubo/289b4e1d6092d3003bc139c469bd41ec533f0fe2/docs/RELEASE_ISSUE_TEMPLATE.md to ipfs/kubo#9237. While copying, I replaced X.Y.Z with 0.16.0.
I got a fresh clone of Kubo:
git clone git@github.com:ipfs/kubo.git
cd kubo, created docs-release-0.16.0 branch and a draft PR for capturing release template improvements.
I linked the docs PR from the main release issue - ipfs/kubo#9237.
I checked what's the latest patch release for CircleCI Go image. It's 1.19.1.
I checked if we should update the image in CircleCI workflow in Kubo. No.
I checked if we should update the image in CircleCI workflow in distributions. No.
I updated the release issue template to include the currently used version - https://github.com/ipfs/kubo/pull/9283/commits/cb706d73c10f8f68dfe19189eb669986e62fa40b.
I checked the boxes in the checklist that asked for CircleCI image upgrade and also added a note next to them on the current version and that no action was required.
I talked with Antonio about the expected RC1 release date. We scheduled a meeting for Thursday to proceed.
We discussed with Antonio open PRs that are supposed to make it into the upcoming release and decided to move the RC to Monday.
I commented on a thread in #ipfs-implementers with information that the RC is moving to Monday. I also added a comment about RC being postponed to the release issue and updated the release schedule in the issue.
I updated the release issue template to include information about checking What's left for release before releasing RC.
I incorporated the RC release flow into the main checklist and updated the checklist in the release issue so that we can test it during this release.
I wonder what's the correct place for Automated Testing section. I also wonder if should make it a rule that we postpone a release only if there are fix: PRs that we're waiting for.