Skip to main content

Release versioning

Each release of the software should have a valid version number. A version number should have the following format: MAJOR.MINOR.PATCH[-PRE-RELEASE-INFO].BUILD_DATE.

For example:

  • 1.5.190.20210319 for a normal release
  • 1.5.190-alpha.20210319 for an alpha release
  • 1.5.190-beta.20210319 for a beta release
  • 1.5.190-rc1.20210319 for a release candidate 1
  • 1.5.190-rc2.20210319 for a release candidate 2

We increment the:

  1. MAJOR version when we add/change major new functionality.
  2. MINOR version when we add/change less important functionality.
  3. PATCH version when we make bug fixes or other subtle changes.

Build date must use the YYYYMMDD format. Pre-release info may be denoted by appending a minus sign and one of the following tags:

  • alpha for a release in an very early development state,
  • beta for a release with most of the required features but with possible/known bugs,
  • rc[number] for a release that is feature complete and with no known bugs.