Releases and versioning - AADevTeam/docs GitHub Wiki

The version numbers closely follow the Semantic Versioning standard. A build number consists of four positive integers in the following format.

w.x.y.z

w - Major version. This is bumped only when a backward incompatible change or a major overhaul to the system is released.

x - Minor version. This is bumped when a new (but backward compatible) change is introduced. Reset to 0 when w is changed.

y - Patch version. This is incremented for each (backward compatible) bug fix or minor change that is released. Reset to 0 when x is changed.

z - Build version. This incremented at each CI run and each time another branch is merged to the dev/QA branch. Reset to 0 when x (not y) is changed.

The version number should be prefixed with the letter v and tagged in git.

eg: v2.8.51.341

The version numbers in the UAT branch may have an rc# suffix, where # is the release candidate version.

eg: v.2.8.51.341-rc2

The version released to the customer should have only the first three digits (w, x, y) as the version number. When either w, x, or y is changed, a release should be created in github with a changelog.

Sample flow: