Releasing Sirius

####1. Make a Release Branch

Create a separate branch for the release, sirius uses semantic versioning:

git branch release-x.x.x
git checkout release-x.x.x

Only two files should change in a release commit, pom.xml and build.sbt. Also only the version number of the project should change in these files.

The commit message should contain every commit from the last release, which should be the output from

git log --pretty --oneline

The commits should be organized into logical sections, for example

• New Features
• Bugfixes
• Documentation/Project Maintenance

The body of the commit message should contain the most important changes since the last release.

See 1bda7c9c for an example.

Once everything has been committed to your fork, send in a pull request for review. ####2. Tag and Release ####3. Build and Deploy Scala Docs ####4. Deploy Scala Artifacts ####5. Increment Version to Next Snapshot