Release policy and versioning

Unblu versions comply with the Semantic Versioning specification. In this scheme, a version’s impact is usually measured with regard to the public API, often referred to as breaking changes.

The version numbers convey information about what has changed from one version to the next. Versions use a sequence of three digits--<major>.<minor>.<patch>(-<qualifier>)--to describe the impact of an update of the software. The meaning of the <major>.<minor>.<patch> version scheme is defined as follows:

Release versions are sparse, for example the next public version after 5.1.6 might be 5.1.9. This only applies to patches. Major or minor versions are incremented successively.

When the version is updated with an increment of the <minor> digit, this is called a new minor version. Once a new minor version is publicly available, there will be no <patch> updates for earlier minor versions. For example, if the last minor version was 5.1.5, there will be no release version 5.1.6 once 5.2.0 has been released.

Features and their related configuration and text properties, web API endpoints, webhooks, and JavaScript methods, enums, and interfaces can have one of three statuses:

Unless stated otherwise, features and their configuration and text properties are stable. Stable configuration and text properties aren’t labeled.

Configuration and text properties with preview or deprecated status are labeled as such in the configuration and text property references, respectively.

In addition to public releases, various internal releases exist during the development phase of a release stream.

The following diagram illustrates the Unblu release cycle:

Unblu supports major versions of the product for 24 months after the first official release date of the superseding major version of the product. This holds true regardless of how many subsequent major releases were made after the respective release.

As outlined above, the versioning scheme introduces no breaking changes in minor versions or patch versions. Customers on the previous major version will therefore be asked to upgrade to the latest minor or patch release to address potential problems with the software.

An upgrade of a minor release or a patch release will never require a migration effort on your part.

The release of Unblu Spark 8 triggered the support countdown for Unblu Collaboration Server v7.

Versions 2 and 3 of the web API were deprecated with the release of Unblu Spark 8 and version 4 of the web API. They won’t be available in Unblu Spark 9.

Releases of the Collaboration Server and the mobile SDKs don’t take place at the same time. To determine whether a particular version of the Collaboration Server is compatible with a particular version of one of the SDKs, follow the guidelines below:

Consider the following example: Android mobile SDK 3.4.2 was released on 14 June 2021. At the time, the latest version of the Collaboration Server was 6.35.0, which was released on 11 June 2021. As a result, Android SDK 3.4.2 is compatible with 6.35.0 and subsequent minor and major versions of Unblu. This is the case until 29 August 2023, when the support period for version 3 of the mobile SDKs ends.

There are no guarantees that Android mobile SDK 3.4.2 is compatible with version 6.34.4 of the Collaboration Server, which was released on 21 May 2021, or earlier versions of the Collaboration Server.