Releases

Version codes: We have four numbers: Mayor, Minor, Patch and Internal: i.e. 2.4.0.2. The last number is only internal, not visible for published versions.

To be documented: Mayor, minor.

Patch versions

• When a patch version is planned, the last internal release will become in the next patch version:
• Update master version code from internal to patch: i.e. 2.4.0.2 will move to 2.4.1.
• Update develop version code to the first internal of the new patch: i.e. 2.4.0.3 will become in 2.4.1.1
• Start publishing process.

Internal releases

• Every release candidate generated after a milestone will be considered at first as an internal release.
• This release will follow all the release workflow, except the publishing process.

Hot fix

• If there is the need to do a hot fix because of a critical issue, a hot fix branch will be created from master in order to fix this explicit issue.
• Once the issue is finished, the hot fix release will merge with master and master into develop.
• Start publishing process.