Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update PATCH_RELEASE_TEMPLATE.md based on 0.13.1 #9095

Merged
merged 7 commits into from Aug 16, 2022
16 changes: 8 additions & 8 deletions docs/PATCH_RELEASE_TEMPLATE.md
@@ -1,8 +1,6 @@
# Patch Release Checklist

This process handles patch releases from version `vX.Y.Z` to `vX.Y.Z+1` assuming that `vX.Y.Z` is the latest released version of go-ipfs.

- [ ] Get temporary permissions to force-push to `release-*` branches
- [ ] Fork a new branch (`release-vX.Y.Z`) from `release` and cherry-pick the relevant commits from master (or custom fixes) onto this branch
- [ ] Use `git cherry-pick -x` so that the commit message says `(cherry picked from commit ...)`
- [ ] Make a minimal changelog update tracking the relevant fixes to CHANGELOG, as its own commit e.g. `docs: update changelog vX.Y.Z+1`
Expand All @@ -14,16 +12,18 @@ This process handles patch releases from version `vX.Y.Z` to `vX.Y.Z+1` assuming
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.
- 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).
- [ ] cut a release on [github](https://github.com/ipfs/go-ipfs/releases) and upload the result of the ipfs/distributions build in the previous step.
- Announce the Release:
- [ ] On IRC/Matrix (both #ipfs and #ipfs-dev)
- [ ] Announce the Release:
- [ ] On discuss.ipfs.io
- This will automatically post to IPFS Discord #ipfs-chatter
- Examples from the past: [0.13.1](https://discuss.ipfs.io/t/go-ipfs-v0-13-1-has-been-released/14599)
- [ ] Pin the topic
- [ ] Release published
- [ ] to [dist.ipfs.io](https://dist.ipfs.io)
- [ ] to [npm-go-ipfs](https://github.com/ipfs/npm-go-ipfs)
- [ ] to [chocolatey](https://chocolatey.org/packages/ipfs)
- [ ] to [snap](https://snapcraft.io/ipfs)
- [ ] to [npm](https://www.npmjs.com/package/go-ipfs) (should be done by [ipfs/npm-go-ipfs](https://github.com/ipfs/npm-go-ipfs), but ok to dispatch [this job](https://github.com/ipfs/npm-go-ipfs/actions/workflows/main.yml) manually)
- [ ] to [chocolatey](https://chocolatey.org/packages/go-ipfs) (should be done by [ipfs/choco-go-ipfs](https://github.com/ipfs/choco-go-ipfs/), but ok to dispatch [this job](https://github.com/ipfs/choco-go-ipfs/actions/workflows/main.yml) manually)
- [ ] to [snap](https://snapcraft.io/ipfs) (should happen automatically, see [snap/snapcraft.yaml](https://github.com/ipfs/go-ipfs/blob/master/snap/snapcraft.yaml))
- [ ] to [github](https://github.com/ipfs/go-ipfs/releases)
- [ ] to [arch](https://www.archlinux.org/packages/community/x86_64/go-ipfs/) (flag it out of date)
- [ ] Cut a new ipfs-desktop release
Expand Down