Skip to main content

Naming policy and lifecycle

To improve BlueMind version tracking, a naming and lifecycle policy has been put in place.

Naming policy​

A BlueMind version includes a major version number and a minor version number, completed by a release number. Numbers are whole numbers that increment numerically.

Major version​

A major release is a new version of the BlueMind solution with very important functional, structural or technical evolutions that are not retroported, e.g. BlueMind 5 with the removal of Cyrus.

Each of these versions is identified by a major version number: BlueMind 4, BlueMind 5, BlueMind 6, etc.

Minor version or BlueMind version​

Minor versions correspond to BlueMind versions. These are major version evolutions with significant functional or technical modifications that have not been retroported, e.g. BlueMind 5.1 with folder sharing functionality.
Each BlueMind version is identified by its major and minor version numbers: BlueMind 4.2, BlueMind 5.1, BlueMind 6.0, etc.

Note: The first minor version X.0 corresponds to a new major version.

Hotfix version​

Patch releases are updates to a minor version that include bug fixes and security patches; for example, BlueMind 5.6.2 includes fixes for the mail, calendar and administration console apps, fixes for integration with third-party and mobile applications (CalDAV, mobile devices, Thunderbird), as well as fixes for DataProtect, MAPI, object storage, etc.

Each patch version is identified by the major version number, the minor version number and a hotfix number: 5.5.17, 5.6.5, 5.7.1, 5.7.2, etc.

Note: The first X.Y.0 release corresponds to a new minor version.

Version life cycle​

Hotfix versions​

Hotfix versions are published regularly, as and when required: discovery of a vulnerability, technical improvements, etc.

Minor versions​

BlueMind minor versions are released approximately every 4 months and continue to be supported after the release of the next version for:

  • 2 months for bug fixes
  • 1 year for security fixes

Security support for the latest minor version of a major version is extended to 18 months after the release of the next major version for security patches.

End of support dates

To find out the end of support dates for a given version, visit the dedicated page: https://forge.bluemind.net/apidoc/

Major versions​

There is no set release schedule for major versions; they are released in line with major product developments.

Support Period

The support for a major version corresponds to the support for its minor versions (see above).