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.

Release​

Releases are evolutions of the minor version with bug and security fixes, e.g. BlueMind 5.0.8 with Imap, Elasticsearch, etc. fixes.

Each release is identified by a major version number, a minor version number and a fix number: BlueMind 4.9.22, BlueMind 5.1.1, BlueMInd 6.0.1, etc.

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

Version life cycle​

Release​

Releases are published regularly, as the need arises.

BlueMind version or minor version​

BlueMind releases are published approximately every 4 months. BlueMind versions are supported 12 months after release :

  • 6 months for bug fixes and security patches
  • then 6 months for security patches.

**The last minor version of a major release has its support 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​

Major releases have no defined release schedule. The support of a major version corresponds to the support of its minor versions, i.e. up to 18 months after the release of the next major version.