chore: remove obsolete PATCH_RELEASE_TEMPLATE.md
galargh committed
Jan 26, 2023 at 16:30 UTC
e1d0e13fe9ca2c0edf35338d85b7c1c69ab64d36
1 file changed
-30
docs/PATCH_RELEASE_TEMPLATE.md
deleted
-30
@@ -1,30 +0,0 @@
1
-# Patch Release Checklist
2
-
3
-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 Kubo.
4
-
5
-- [ ] Get temporary permissions to force-push to `release-*` branches
6
-- [ ] Fork a new branch (`release-vX.Y.Z`) from `release` and cherry-pick the relevant commits from master (or custom fixes) onto this branch
7
- - [ ] Use `git cherry-pick -x` so that the commit message says `(cherry picked from commit ...)`
8
-- [ ] Make a minimal changelog update tracking the relevant fixes to CHANGELOG, as its own commit e.g. `docs: update changelog vX.Y.Z+1`
9
-- [ ] version string in `version.go` has been updated (in the `release-vX.Y.Z+1` branch), as its own commit.
10
-- [ ] Make a PR merging `release-vX.Y.Z+1` into the release branch
11
- - This may be unnecessary, e.g. for backports
12
-- [ ] Tag the merge commit in the `release` branch with `vX.Y.Z+1` (ensure the tag is signed)
13
-- [ ] Add artifacts to https://dist.ipfs.tech/kubo
14
- 1. Make a PR against [ipfs/distributions](https://github.com/ipfs/distributions) with local changes produced by `add-version` (see [usage](https://github.com/ipfs/distributions#usage))
15
- 2. Wait for PR to build artifacts and generate diff
16
- 3. Inspect results, merge if CI is green and the diff looks ok
17
- 4. Wait for `master` branch to build and update DNSLink at https://dist.ipfs.tech
18
-- [ ] Cut a release on [github](https://github.com/ipfs/kubo/releases) and reuse signed artifacts from https://dist.ipfs.tech/kubo (run [sync-release-assets.yml workflow](https://github.com/ipfs/kubo/actions/workflows/sync-release-assets.yml)).
19
-- [ ] Announce the Release:
20
- - [ ] On [discuss.ipfs.tech](https://discuss.ipfs.tech)
21
- - This will automatically post to Matrix (`#lobby:ipfs.io`) and IPFS Discord (`#ipfs-chatter`)
22
- - Examples from the past: [0.13.1](https://discuss.ipfs.tech/t/go-ipfs-v0-13-1-has-been-released/14599)
23
- - [ ] Pin the discuss topic
24
-- [ ] Release published
25
- - [ ] to [dist.ipfs.tech](https://dist.ipfs.tech)
26
- - [ ] to [npm-go-ipfs](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)
27
- - [ ] to [github](https://github.com/ipfs/kubo/releases)
28
- - [ ] to [arch](https://www.archlinux.org/packages/community/x86_64/go-ipfs/) (flag it out of date)
29
-- [ ] Cut a new ipfs-desktop release
30
-- [ ] Merge the `release` branch back into `master`, ignoring the changes to `version.go` (keep the `-dev` version from master).