update release list with checkpoints bump (#4800)

This commit is contained in:
Alfredo Garcia 2022-07-21 00:44:40 -03:00 committed by GitHub
parent 81727d7df0
commit 21d3af4b8d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 1 deletions

View File

@ -99,6 +99,12 @@ We should update the README to:
- [ ] Update the "Build and Run Instructions" with any new dependencies. - [ ] Update the "Build and Run Instructions" with any new dependencies.
Check for changes in the `Dockerfile` since the last tag: `git diff <previous-release-tag> docker/Dockerfile`. Check for changes in the `Dockerfile` since the last tag: `git diff <previous-release-tag> docker/Dockerfile`.
## Checkpoints
With every release and for performance reasons, we want to update the zebra checkpoints. More information on how to do this can be found in [the zebra-checkpoints README](https://github.com/ZcashFoundation/zebra/blob/main/zebra-consensus/src/checkpoint/README.md).
To do this you will need a synchronized `zcashd` node. You can request help from other zebra team members to submit this PR if you can't make it yourself at the moment of the release.
## Change Log ## Change Log
**Important**: Any merge into `main` deletes any edits to the draft changelog. **Important**: Any merge into `main` deletes any edits to the draft changelog.
@ -134,8 +140,9 @@ From "Keep a Changelog":
### Create the Release PR ### Create the Release PR
After you have the version increments and the updated changelog: After you have the version increments, the updated checkpoints and the updated changelog:
- [ ] Make sure the PR with the new checkpoint hashes is already merged.
- [ ] Push the version increments and the updated changelog into a branch - [ ] Push the version increments and the updated changelog into a branch
(name suggestion, example: `v1.0.0-alpha.0-release`) (name suggestion, example: `v1.0.0-alpha.0-release`)
- [ ] Create a release PR by adding `&template=release-checklist.md` to the - [ ] Create a release PR by adding `&template=release-checklist.md` to the