This implementation guide is in currently in an alpha state at the moment. This means that changes and releases are occuring regularly.
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
A pre-release version MAY be denoted by appending a hyphen (refer to Semantic Versioning - Item 9)
For examples: 1.0.0-alpha.1 is a valid pre-release version.
The following pre-release labels will be used across all products:
||Complete enough for internal testing.|
||early||Complete enough for external testing.|
||late||Complete enough for external testing. Usually feature complete.|
||Almost ready for final release. No new feature enhancements.|
rc = Release Candidate.