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
Update docs: Release management in Git/Github #5269
Conversation
1. A new release branch is created `release/celo-core-contracts/${N}` with the contracts to be audited. | ||
2. The latest commit on the release branch is tagged with `celo-core-contracts-v${N}.pre-audit`. | ||
3. On Github, a pre-release Github release should be created pointing at the latest tag on the release branch. | ||
4. On master branch, `.circleci/config.yml` should be edited so that the variable `RELEASE_TAG` points to the tag `celo-core-contracts-v${N}.pre-audit` so that all future changes to master are versioned against the new release. |
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.
new info
|
||
After a completed release process: | ||
1. The release branch should be merged into `master` with a merge commit (instead of the usual squash merge strategy). | ||
2. On master branch, `.circleci/config.yml` should be edited so that the variable `RELEASE_TAG` points to the tag `celo-core-contracts-v${N}.mainnet` |
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.
new info
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.
🙏 This is amazing!
Description
Update Release Process docs with git management for comparing versioned contracts
Other changes
change variable name to reflect new tag-oriented approach. slight reformat of entire section to be more checklist oriented.
Tested
N/A
Related issues
Backwards compatibility
yes