Search loading...


Explore and Make use of Nationally Defined Messaging APIs


Guide Versioning

An overview of this implementation guide is versioned.

Semantic Versioning

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.

Pre-release Labels

The following pre-release labels will be used across all products:

Pre-release Label Lifecycle Description
alpha   Complete enough for internal testing.
beta early Complete enough for external testing.
beta late Complete enough for external testing. Usually feature complete.
rc   Almost ready for final release. No new feature enhancements.

rc = Release Candidate.

Tags: development

All content is available under the Open Government Licence v3.0, except where otherwise stated