Beta and GA Releases

When a new major version of Hippo CMS is released, first, a Beta version will be released, followed by a General Availability (GA) version.

Beta

(Prior to Hippo CMS 12, Beta was referred to as First Customer Shipment or FCS)

The primary purpose for the Beta version of the new major release is to harden it in order to make it GA. A Beta version can and should be used for the following purposes:

  • Selected customers can use the beta version in production for new projects, and based on explicit agreement with/awareness of Hippo CMS engineering before the project is started.

  • Hippo CMS project developers can start using the documented new functionality on the preferred stack for starting new Hippo CMS implementations, as well as for thinking about how they are going to leverage the new functionality within existing, to-be-upgraded Hippo CMS implementations

  • BloomReach can showcase and demo the complete set of new features.

Compared to the GA version, the Beta version has the following limtations:

  • Existing Hippo CMS implementations have to wait for the GA release to start upgrading.

  • Upgrade documentation and tooling is only available with the GA version.

  • The beta version is not guaranteed to be (API-) compatible with the GA version.

  • The beta version has not yet been fully validated in scenarios other than the preferred stack, including (but not limited to) other containers (e.g. WebLogic) other databases (e.g. Oracle, MsSQL), other browsers (e.g. Safari, Edge) etc.

  • Localized labels for supported languages other than English may not yet be available in the Beta version.

  • The beta version is not guaranteed to work flawlessly on all browsers supported by the GA version.

If you're interested in using the Beta release for your project, please contact BloomReach Support.

GA - General Availability

Primary purpose: all projects can use this release in production.

The major improvements of the GA release over the Beta release:

  • Stability, e.g. bug fixes - the GA release has no known Blocker or Top issues
  • Upgrade documentation and tooling are made available to customers that have a BloomReach Experience subscription
  • Translations for all supported languages are available
  • Support for containers other than Tomcat, e.g. Oracle Weblogic (Enterprise subscription required)
  • Full and specific server requirements including processor, memory and storage are published

The amount of time between the Beta and GA releases is typically two to three months.