Application versioning

← All Topics

We commonly get questions about the versioning we use on our system applications. We are constantly innovating and updating our solutions to ensure that our customers are always benefiting from our innovations as we develop them.

Advanced solutions uses semantic versioning as described well by Tom Preston-Werner in his white paper (references below).

Summary – (In Plain language)

A version is made up of three components, for example given an application version of 1.0.8

  • 1 refers to the Major version
  • 0 refers to the minor version
  • 8 refers to the patch level

The changing of these version has the following significance, note explained in reverse order.

  • Patch level – Changes to patch level only include bug fixes. A bug fix is defined as an internal change that fixes incorrect behaviour.
  • Minor version – is incremented when new backward compatible functionality is introduced. This means our APIs and components continue to work, it might be that the new functionality is not completely available without an update but there is no impact to continue to use existing features.
  • Major version – When new features are added that make the component incompatible with the other integrated solutions or components that are not updated, this is considered a major version. This might entail a change to our API for example to add required fields necessary for the solution to continue working. in an example such as this we require all components of our solution to be updated at the same time.

Note for customers on support, solution notices are sent out for any Minor or Major version update with instructions on how to perform an update. Patch level updates are updated as soon as we are made aware of any bug in our solutions and released or made available automatically through the normal channels.

For clarification or if you have any questions feel free to reach out.

Applies to


Semantic Versioning

Pin It on Pinterest