Skip to content

Release workflow

Szilard Ledan edited this page Jun 11, 2016 · 2 revisions

About the versioning

Example of a version: 1.3.10, where:

  • the first number means the Public API version,
  • the second number means the internal stable releases,
  • the third number means the non-stable versions (milestones).

Release periods

Between releases there is an average ninety days period, because the gestation of gepard (cheetah) is nearly three months long.

Release issue (template)

On every release need to be create an issue. It is a release closer ticket. If all issues are ready on a release-version than open this closer ticket and update/fix/etc. before release that version.

Release closer ticket template

Title:

Release <API>.<R>.<V>

Note: where means the Public API version, the means the internal stable releases and the means the non-stable versions (milestones).

Descriptions:

TODO: @szledan

Labels:

critical, important, enhancement