Add a Release Process for SDK (#1803)
* Add docs/RELEASE_PROCESS.md * Address PR comments
This commit is contained in:
parent
6c7e17a5de
commit
12ef51dc7a
|
@ -8,7 +8,7 @@ v If a checkbox is n/a - please still include it but + a little note why
|
|||
- [ ] Updated all relevant documentation (`docs/`)
|
||||
- [ ] Updated all relevant code comments
|
||||
- [ ] Wrote tests
|
||||
- [ ] Added entries in `PENDING.md`
|
||||
- [ ] Added entries in `PENDING.md` that include links to the relevant issue or PR that most accurately describes the change.
|
||||
- [ ] Updated `cmd/gaia` and `examples/`
|
||||
___________________________________
|
||||
For Admin Use:
|
||||
|
|
|
@ -0,0 +1,11 @@
|
|||
### `cosmos/cosmos-sdk` Release Process
|
||||
|
||||
- [ ] 1. Decide on release designation (are we doing a patch, or minor version bump) and start a P.R. for the release
|
||||
- [ ] 2. Add commits/PRs that are desired for this release **that haven’t already been added to develop**
|
||||
- [ ] 3. Merge items in `PENDING.md` into the `CHANGELOG.md`. While doing this make sure that each entry contains links to issues/PRs for each item
|
||||
- [ ] 4. Summarize breaking API changes section under “Breaking Changes” section to the `CHANGELOG.md` to bring attention to any breaking API changes that affect RPC consumers.
|
||||
- [ ] 5. Tag the commit `{{ .Release.Name }}-rcN`
|
||||
- [ ] 6. Kick off 1 day of automated fuzz testing
|
||||
- [ ] 7. Release Lead assigns 2 people to perform buddy testing script
|
||||
- [ ] 8. If errors are found in either #6 or #7 go back to #2 (*NOTE*: be sure to increment the `rcN`)
|
||||
- [ ] 9. After #6 and #7 have successfully completed then merge the release PR and push the final release tag
|
Loading…
Reference in New Issue