|
%!s(int64=4) %!d(string=hai) anos | |
---|---|---|
.. | ||
README.md | %!s(int64=4) %!d(string=hai) anos | |
cherry-pick-pr | %!s(int64=10) %!d(string=hai) anos | |
const.py | %!s(int64=5) %!d(string=hai) anos | |
generate_changelog.sh | %!s(int64=5) %!d(string=hai) anos | |
release.md.tmpl | %!s(int64=7) %!d(string=hai) anos | |
release.py | %!s(int64=5) %!d(string=hai) anos | |
utils.py | %!s(int64=5) %!d(string=hai) anos | |
utils.sh | %!s(int64=8) %!d(string=hai) anos |
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-compose
s release notes and version on github documentation repository: