Release 0.4.0
Changes to do on the master branch before releasing:
-
update/review docs/*
and make sure it matches the current state- Update how to checkout the latest stable tag
-
Update dependencies in requirements-stable.txt
- Create a new
virtualenv
and activate it - Run
pip3 install -r requirements.txt
- Run
pip3 freeze > requirements-stable.txt
- Create a new
-
update CHANGELOG.md - Include
Known issues
- Include
-
update the version number in the VERSION
file -
commit (signed) -
Push to MR, including tag
Then, create a release branch, pin deps, and tag the release:
-
If this is a major release, create a new release branch ( v0.4
, etc.). -
Ensure all dependencies are updated and locked (locking should be done only on the release branch): -
chart versions in flux/*
-
Release new version of single-sign-on and pin that release too single-sign-on#55 (closed)
-
-
in ansible/group_vars/all/oas.yml
:flux_source.branch
should be set to the release branch
-
-
create signed tag ( git tag -s 0.2.0 -m 'Release 0.2.0'
) -
Log into readthedocs.org and update documentation for tagged versions