fix order of events in the release process
We need to gx release *before* tagging. License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
Steven Allen committed
Sep 6, 2018 at 13:43 UTC
ed256a949c28f2182d1eefc880d2b610aea17d0a
1 file changed
+2
-2
docs/releases.md
+2
-2
@@ -23,11 +23,11 @@ will be allowed up to release day.
23
- [ ] CHANGELOG.md has been updated
24
- use `./bin/mkreleaselog` to generate a nice starter list
25
- [ ] version string in `repo/version.go` has been updated
26
+- [ ] publish gx version with `gx release`, as per [gx release guidelines](https://github.com/whyrusleeping/gx#publishing-and-releasing)
27
- [ ] tag commit with vX.Y.Z
27
-- [ ] update release branch to point to release commit
28
+- [ ] update release branch to point to release commit (`git merge vX.Y.Z`).
29
- [ ] publish dist.ipfs.io
30
- [ ] publish next version to https://github.com/ipfs/npm-go-ipfs
30
-- [ ] publish gx version with `gx release`, as per [gx release guidelines](https://github.com/whyrusleeping/gx#publishing-and-releasing)
31
32
## Post-Release
33
- [ ] Bump version string in `repo/version.go` to `vX.Y.Z-dev`