Making releases¶
Preparation¶
Git¶
The following describes the steps for a new release series (like 1.1.x
).
For patch releases of LTS versions, replace the dev
branch with another temporary branch and master
with lts/...
.
Rebase the dev
branch to the master
first.
Then, check that the version is correctly set in the following files.
It needs to be the latest version of the master
branch (like 1.0.2
).
.bumpversion.cfg
src/version.txt
A commit of the changes is not necessary.
Then create the new version:
bump2version --allow-dirty major|minor|patch
Check the git log:
There should be a new commit and tag.
The commit should only change the version in the two files listed above, nothing else.
Push the branch, but not the tag:
git push
Create a pull request on Github, so that the final code quality checks are started.
If this is ok, merge the branch and also push the tags:
git checkout master
git merge dev
git push
git push --tags
Docker¶
The, the Docker container need to be build, tested and pushed:
First, build the container from scratch:
./scripts/docker.sh build
Then run it to see if every services starts, check http://localhost:8000 in your browser:
./scripts/docker.sh test
If that worked, push the new container:
./script/docker.sh push
Git cleanup¶
In the dev
branch, the version in src/vesion.txt
needs to be set to dev
again.
Commit this change to the dev
branch.