Skip to content

VariaMos versioning strategy

lufe089 edited this page Oct 6, 2017 · 6 revisions

                                 `major.minor.development_stage.patch`

  • major: version when incompatible API changes are made
  • minor: version when functionality in a backwards-compatible manner are added
  • development stages:
    • 0 for alpha: early stage, only tested by developers. This version is inestable, might have bugs and missing features
    • 1 for beta: mature but not ready for release, it might contain known and unknown bugs. Available for testing by community members
    • 2 for release candidate: beta version with potential to be a final product. The release candidate will become a relase when the developer team agrees that no new source code will be added.
    • 3 for final release
  • patch: version when you make backwards-compatible bug fixes.

Examples

  • 1.0.0.1 alfa version patch 1 (also 1.0-a1)
  • 1.0.1.20 beta with some bug fixes and menor improvements (also 1.0-b20)
  • 1.0.2.0 release candidate (also 1.0-rc0)
  • 1.0.3.0 commercial distribution (also 1.0-r)
  • 1.0.3.5 commercial distribution with many bug fixes (also 1.0-r5)

Sources:

https://en.wikipedia.org/wiki/Software_versioning#Number_of_sequences
https://en.wikipedia.org/wiki/Software_release_life_cycle