|
|
4 years ago | |
|---|---|---|
| .. | ||
| README.md | 4 years ago | |
| cherry-pick-pr | 10 years ago | |
| const.py | 5 years ago | |
| generate_changelog.sh | 5 years ago | |
| release.md.tmpl | 7 years ago | |
| release.py | 5 years ago | |
| utils.py | 5 years ago | |
| utils.sh | 8 years ago | |
The release process is fully automated by Release.Jenkinsfile.
./script/release/release.py tag <version>By appropriate, we mean for a version 1.26.0 or 1.26.0-rc1 you should run the script in the 1.26.x branch.
The script should check the above then ask for changelog modifications.
After the executions, you should have a commit with the proper bumps for docker-compose version and run.sh
Run git push --tags upstream <version_branch>
This should trigger a new CI build on the new tag. When the CI finishes with the tests and builds a new draft release would be available on github's releases page.
Check and confirm the release on github's release page.
In case of a GA version, please update docker-composes release notes and version on github documentation repository: