@@ -24,14 +24,12 @@ We might expand the six week release schedule in case of:
...
@@ -24,14 +24,12 @@ We might expand the six week release schedule in case of:
Before this stage, we expect _all_ tests (interop, testlab, performance, etc.) to pass.
Before this stage, we expect _all_ tests (interop, testlab, performance, etc.) to pass.
At this stage, we'll:
At this stage, we'll:
- 1. Start a partial-rollout to our own infrastructure.
1. Start a partial-rollout to our own infrastructure.
- 2. Test against ipfs and ipfs-shipyard applications.
2. Test against ipfs and ipfs-shipyard applications.
**Goal(s):**
**Goal(s):**
- 1. Make sure we haven't introduced any obvious regressions.
1. Make sure we haven't introduced any obvious regressions.
- 2. Test the release in an environment we can monitor and easily roll back (i.e., our own infra).
2. Test the release in an environment we can monitor and easily roll back (i.e., our own infra).
### Stage 2 - Public Beta
### Stage 2 - Public Beta
...
@@ -55,84 +53,7 @@ At this stage, the release is "battle hardened" and ready for wide deployment.
...
@@ -55,84 +53,7 @@ At this stage, the release is "battle hardened" and ready for wide deployment.
## Performing a Release
## Performing a Release
The first step is for the `Lead Maintainer` for `go-ipfs` to open an issue with Title `go-ipfs <version> Release` and a c&p of the following template:
The first step is for the `Lead Maintainer` for `go-ipfs` to open an issue with Title `go-ipfs <version> Release` and a c&p of the [RELEASE_ISSUE_TEMPLATE](./RELEASE_ISSUE_TEMPLATE.md)
```
> <short tl;dr; of the release>
# 🗺 What's left for release
<List of items with PRs and/or Issues to be considered for this release>
# 🔦 Highlights
<List of items with PRs and/or Issues included for this release>
# 🏗 API Changes
<List of API changes, if any>
# ✅ Release Checklist
For each RC published in each stage:
- version string in `version.go` has been updated
- tag commit with vX.Y.Z-rcN
- [ ] Stage 1 - Internal Testing
- [ ] Feature freeze. If any non-trivial features get added to the release, uncheck all the checkboxes and return to this stage.
- [ ] CHANGELOG.md has been updated
- use `./bin/mkreleaselog` to generate a nice starter list
- use `./doc/RELEASE_TEMPLATE.md` as a template
- [ ] Automated Testing (already tested in CI) - Ensure that all tests are passing, this includes:
- [ ] Deploy new version to a subset of Bootstrappers
- [ ] Deploy new version to a subset of Gateways
- [ ] Deploy new version to a subset of Preload nodes
- [ ] Collect metrics every day. Work with the Infrastructure team to learn of any hiccup
- [ ] IPFS Application Testing - Run the tests of the following applications:
- [ ] WebUI
- [ ] IPFS Desktop
- [ ] IPFS Companion
- [ ] NPM on IPFS
- [ ] Stage 2 - Public Beta
- [ ] Reach out to the IPFS _early testers_ listed in `docs/EARLY_TESTERS.md` for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR.
- [ ] Reach out to on IRC for beta testers.
- [ ] Run tests available in the following repos with the latest beta (check when all tests pass):
