How are Bloomreach Experience Manager versions numbered?
Bloomreach Experience Manager uses the Semantic Versioning Scheme.
This version numbering scheme allows Bloomreach to release multiple minor versions per year that bring you new features in a backward compatible fashion, while at the same time provide you with enough room to hold onto a major version if you do not want to go through a full major release update yet.
What is the semantic versioning scheme?
In the Semantic Versioning Scheme, software releases have the format of three numbers, separated by dots. For example:
In general, this takes the form of
- The MAJOR version number is issued to introduce new functionality or changes in the system and/or architecture that could break backwards compatibility with previous versions or might introduce incompatible API changes. Major releases will be issued approximately once a year.
- In a MINOR version, we introduce new functionality in a less invasive way; backwards compatibility with the major version is not affected. Minor releases will be issued a number of times per year.
- A PATCH version is mainly intended for small changes or bug fixes only. This is done in a backwards compatible way with the major version. Patch releases will be issued approximately every 1-2 months.
Note: In many cases, the patch version is omitted in conversations and text. For example, Bloomreach Experience Manager version 14.1 implicitly refers to the most recent patch version of this release, e.g. 14.1.5 if that is the most recent release.
Bloomreach Experience Manager artifact version numbers
Internally, Bloomreach Experience Manager is composed of several artifacts. All artifact version numbers are aligned with the corresponding Bloomreach Experience Manager release.
Maintenance versions are backward compatible. Minor versions might not be. Look at the release notes for upgrade instructions and API changes.