Skip to content

Release process

Neraste edited this page Sep 8, 2019 · 5 revisions

Release a new Dakara server version

Create the new version

Move to the develop branch and pull. If there are cosmetic modifications to perform on the changelog file, do it now. Call the bump version script:

./bump_version.sh 0.0.0 0.1.0

with 0.0.0 the release version number and 0.1.0 the next version (without 'v', without '-dev').

Push the version commit and its tag:

git push
git push origin 0.0.0

with the according version number.

Move to the master branch and merge created tag into it. Then push.

git checkout master
git pull
git merge 0.0.0
git push

Create the release

Before creating the server bundle, make sure dependencies are up to date:

pip install -r requirements.txt

Call the script to create the archive:

./create_archive.sh 0.0.0 9.9.9

with 0.0.0 the according version number and 9.9.9 the corresponding Dakara web client version number.

On GitHub, draft a new release, set the version number with the created tag ("Existing tag" should read). Set the release title with "Version 0.0.0" (with number, you get it?). Copy-paste corresponding section of the changelog file in the release description. Add the created archive file.

You can now publish the release.

Clone this wiki locally