Releases Workflow

-- Work in Progress --

General information

• Develop always contains the code that will at some point go to the next Release.

Versioning Scheme

Our versioning follows the syntax of semantic versioning. That means each version is identified by 3 numbers separated by a dot and appearing as MAJOR.MINOR.PATCH. e.g. 1.1.3.

Additional suffixes or labels may follow those 3 numbers. They should be separated by a -, eg. 1.1.3-rc1. Note that for Ubuntu packages that separator has to differ and will be a tilda ~ and as such the corresponding ubuntu example package version would be 1.1.3~rc1.

Actions taken for a release

• Merge Develop branch to release.
• Increment develop's CMakeLists's version to the next version Note: Could be done automatically by Jenkins.
• Start a Jenkins Release build, specifying the version as a parameter. Note: Such a Jenkins job is not yet ready.
• If the build succeeds Jenkins should tag the version given as a parameter, push the tag to umbrella and upload the binaries to https://build.ethdev.com/cpp-binaries-data/ under a new directory with the given version name.