GitLab

Release versioning convention:

• Major version update (1.0 -> 2.0) when including significantly new functionality, where changes are not compatible with previous versions
• Minor version update (1.0 -> 1.1) when adding new functionality that remain backwards compatible
• Patch version update (1.0 -> 1.0.1) when adding patches that remain backwards compatible

Steps required to make a new release

1. Merge all changes into the Development branch
2. Make sure all unit tests and doc tests are passing successfully on the GitLab server
3. Make sure all tutorials are working; if necessary update tutorials and copy new html files to the appropriate folder in the ketos docs section.
4. Update the change log (docs/source/versions/changelog.rst)
5. Update the version number in setup.py and docs/source/conf.py
6. Commit and push changes from step 4 and 5 to the Development branch
7. Build the documentation:

cd docs/
make html

8. Review the documentation
9. Create a merge request for the Development branch into the master branch
10. Once this merge request has been reviewed and accepted, upload the new version to PyPI:

python setup.py sdist bdist_wheel
twine upload dist/ketos-X.Y.Z.tar.gz

11. Finally, upload the documentation to the docs server:

cd docs
./upload.sh