Semantic Versioning for Cognigy.AI

Topic: 
|
3 min read
Sebastian Glock
Authors name: Sebastian Glock April 20, 2021

At Cognigy, we always aim to speed up the time-to-market for new features, improvements, and fixes. We update our SaaS environments every few days and simultaneously provide update packages to our on-premises customers.

MicrosoftTeams-image (8)-1

 

Semantic Versioning

To make it easier for customers to keep track of any change in the platform, we now follow Semantic Versioning (Semver) to name Cognigy.AI software releases.

In a nutshell, we will stick to the MAJOR.MINOR.PATCH format and apply the following rules. Incrementing the...

  • MAJOR number indicates incompatible API changes
  • MINOR number indicates added functionality in a backward-compatible manner
  • PATCH number indicates a release that only has backward-compatible bug fixes.

With this approach, MINOR will count up much faster than in the past. There is no cap or rollover to MAJOR: MINOR can have two or three digits and is only ever reset with the release of a new major version.

Also, a new major version is not necessarily a “big bang release” providing a whole new software experience – it might be that business users do not notice a major update, but developers need to account for a small (but non-compatible) API change.

What’s does that mean for you as a Cognigy.AI customer?

All users will continue to benefit from continuous, incremental & hassle-free updates. SaaS customers will always be on the latest & greatest version of Cognigy.AI and learn about improvements from mails, tooltips, and other channels. Finally, on-premises operators can now easier than ever identify the impact of an update before provisioning it on their servers.

 

Reach out to us if you have any questions or if you would like to share your thoughts.
image119-1
image119-1
image119-1
Close

Request a demo!