-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
tweak the release process #6553
Conversation
Stebalien
commented
Aug 2, 2019
- Split out automated testing into a stage 0.
- Flesh out release cycle.
- Define the process for normal patch releases.
We do automated testing before we test on infra, etc. Make that explicit.
docs/releases.md
Outdated
## Performing a Release | ||
|
||
The release is managed by the `Lead Maintainer` for `go-ipfs`. It starts with the opening of an issue containing the content available on the [RELEASE_ISSUE_TEMPLATE](./RELEASE_ISSUE_TEMPLATE.md). Then, the 4 stages will be followed until the release is done. | ||
The release is managed by the `Lead Maintainer` for `go-ipfs`. It starts with the opening of an issue containing the content available on the [RELEASE_ISSUE_TEMPLATE](./RELEASE_ISSUE_TEMPLATE.md). Then, the 5 stages will be followed until the release is done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
an issue on go ipfs with a certain tag? Do we also want to communicate the opening of that release elsewhere such that it notifies people who maybe don't want to follow all go-ipfs releases (like a "pre-release" RC on github?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added a github tag ("release") and an item to the checklist for cutting a prerelease using through github (so users can subscribe to releases).
Co-Authored-By: MollyM <momack2@users.noreply.github.com>
Co-Authored-By: Alan Shaw <alan.shaw@protocol.ai>