Skip to content

Latest commit

 

History

History
31 lines (21 loc) · 1.52 KB

RELEASING.md

File metadata and controls

31 lines (21 loc) · 1.52 KB
Raw

Releasing new version

Step-by-step

In order to release a new version, there are several steps that must happen:

  1. make sure all issues (in GitHub and in JIRA) targeted to the version are resolved
  2. create a pull request in which you change the version string according to the format described in another section
  3. get review and merge the pull request
  4. release the version through GitHub release functionality with a new tag corresponding to the version string from the pull request (create the tag during the release through the release dialog)
  5. mark the corresponding version1 released in JIRA as well

Version naming conventions

Version string must have the following format:

  • major.minor.micro.Dev
  • major.minor.micro.Alpha<number>
  • major.minor.micro.Beta<number>
  • major.minor.micro.CR<number>
  • major.minor.micro.Final

where <number> is a mandatory numerical value starting from 1. Any version marked Final must not have a number. If there is any issue with such a version, just increase a micro version and go through the process again.

Versions in between of x.y.z.Final and next a.b.c.Alpha1 will be called a.b.c.Dev.

Footnotes

  1. The corresponding version within the JIRA project has native- prefix. For example version 2.0.0.Final in this repository will be native-2.0.0.Final in the JIRA project. ↩