End of Life Policy - Enterprise Java Content management system - Hippo CMS

End of Life Policy

EOL, Updates and Support

Hippo CMS Life Cycle

  • The two most recent minor versions for the current major version are actively maintained.
    For example: If version 12.4 is the most recent Hippo version, this means that versions 12.4 and 12.3 are actively maintained.

  • Additionally, for the two most recent major versions before the current major version, only the final minor versions are actively maintained.
    For example: If the most recent release is Hippo CMS somewhere in the 12.x range, the final minor versions of 11.x and 10.x are actively maintained.

  • For customers with a standard enterprise license, BloomReach provides support for the current and the previous major version. For customers with a premium enterprise license, Hippo provides support for the current and the two previous major versions.

The Release Notes Overview lists which versions are currently supported (and under which license) and which versions have reached End-of-Life status.

Advice to Customers

  • For new customers we will advise to start on the most recent minor release and follow updates till the next major version is released. At that point, the customer can choose to remain on the final minor for a while, or to upgrade to the next major version and continue to follow the ‘minor track’. What option to choose depends on the customer preference.

  • When you are an existing customer and you are running a final minor from an older release, we advise you to update to the previous or latest minor version, or wait till a new final minor becomes available.

Upgrade Notes

Several upgrade paths are supported, as documented on the website for customers having a support contract.

End of Life Policy

EOL, Updates and Support

Hippo CMS Life Cycle

  • The two most recent minor versions for the current major version are actively maintained.
    For example: If version 12.4 is the most recent Hippo version, this means that versions 12.4 and 12.3 are actively maintained.

  • Additionally, for the two most recent major versions before the current major version, only the final minor versions are actively maintained.
    For example: If the most recent release is Hippo CMS somewhere in the 12.x range, the final minor versions of 11.x and 10.x are actively maintained.

  • For customers with a standard enterprise license, BloomReach provides support for the current and the previous major version. For customers with a premium enterprise license, Hippo provides support for the current and the two previous major versions.

The Release Notes Overview lists which versions are currently supported (and under which license) and which versions have reached End-of-Life status.

Advice to Customers

  • For new customers we will advise to start on the most recent minor release and follow updates till the next major version is released. At that point, the customer can choose to remain on the final minor for a while, or to upgrade to the next major version and continue to follow the ‘minor track’. What option to choose depends on the customer preference.

  • When you are an existing customer and you are running a final minor from an older release, we advise you to update to the previous or latest minor version, or wait till a new final minor becomes available.

Upgrade Notes

Several upgrade paths are supported, as documented on the website for customers having a support contract.