Ulysses Souza 203576363e Remove section mentioning _config_authoring on docs il y a 4 ans
..
README.md 203576363e Remove section mentioning _config_authoring on docs il y a 4 ans
cherry-pick-pr c4f0f24c57 Fix release script notes about software and typos. il y a 10 ans
const.py 8ce743c8c1 Fixed new things that came after the PR il y a 5 ans
generate_changelog.sh 4bf623d53d Merge pull request #7163 from ndeloof/changelog il y a 5 ans
release.md.tmpl 8493540a1c Reffer Docker for Mac and Windows as Docker Desktop il y a 7 ans
release.py c90ba119f5 Fix tox failures il y a 5 ans
utils.py 4d3d9f64b9 Removed Python2 support il y a 5 ans
utils.sh 27297fd1af fix a typo in script/release/utils.sh il y a 8 ans

README.md

Release HOWTO

The release process is fully automated by Release.Jenkinsfile.

Usage

  1. In the appropriate branch, run ./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

  1. 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.

  2. Check and confirm the release on github's release page.

  3. In case of a GA version, please update docker-composes release notes and version on github documentation repository: