Version Numbering

How are Hippo CMS versions numbered?

Starting in 2015, we switched to using the Semantic Versioning Scheme, with CMS 10.0 as the next major version after CMS 7.9.

This new version numbering scheme allows Hippo 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.

Why this jump from 7 to 10?

We decided not to move to Hippo CMS 8.x, as this would effectively mix the old numbering and new numbering systems seamlessly together and therefore would cause confusion; 7.9 and 8.0 would seem to belong to the same version numbering scheme but the digits would have completely different meaning. The move from 7 to 10 avoids this confusion.

What is this new version numbering scheme?

In the Semantic Versioning Scheme, software releases have the format of three numbers, separated by dots, with an optional label added, e.g.:

10.0.2 GA

In general, this takes the form of 

MAJOR.MINOR.PATCH <label>

  • 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.
  • An additional <label> can be used to add meta data like labels for pre-release or release, i.e. 'FCS' or 'GA'.  

Note: In many cases, the patch version is omitted in conversations and text. We then speak or write about e.g. Hippo CMS version 10.3. We then implicitly mean the most recent patch version of this release, e.g. 10.3.5, if that is the most recent release.

The versioning scheme up to Hippo CMS 7.9

The version numbering schema up to Hippo CMS 7.9 works as follows: 

Let's take for example: Hippo CMS 7.9.1. This results into the following table:

Version   Name Definition Frequency

7

architecture version number   

Hippo CMS product version number 7

not changed, no longer applicable with Hippo CMS 10

7. 9

(major) version number

The 7.9   release of Hippo CMS

Once or twice a year

7.9. 1

maintenance version number  

Maintenance update of the 7.9 release

Monthly

Starting from December 19th, 2008, after the release of Hippo CMS 7.0, the leading version number was the Hippo CMS product number 7.

Hippo CMS artifact version numbers

Internally the Hippo CMS Suite is composed of several artifacts each with its own version schema. See the following pages  CMS, HSTTWO and  REPO in Jira about their version numbers and their release dates. In general these number start with a 2. Maintenance versions are backward compatible. Minor versions might not be. Look at the release notes for upgrade instructions and API changes.

In general you should stick to the latest maintenance release. Picking up artifacts that are newer than as specified in the maintenance release requires thorough testing on your side. When we have tested the artifact and assessed it as reliable, we will incorporate it into the maintenance release.

Hippo CMS releases and corresponding artifact version numbers

Release   

Release date   

CMS version     

HST2 version      

Repo version    

Go Green version      

Archetype version

11.1 Oct 31, 2016 4.1.x 4.1.x 4.1.x n/a 4.1.x
11.0 July 5, 2016 4.0.x 4.0.x 4.0.x n/a 4.0.x
10.2 Feb 7, 2016 3.2.x 3.2.x 3.2.x n/a 3.2.x
10.1 Nov 1, 2015 3.1.x 3.1.x 3.1.x n/a 3.1.x
10.0 July 14, 2015 3.0.x 3.0.x 3.0.x n/a **) 3.0.x

7.9

Apr 15, 2014

2.26.x

2.28.x

2.26.x

3.09.x

2.00.x

7.8

Dec 12, 2012

2.24.x

2.26.x

2.24.x

3.07.x

1.07.x

7.7

Dec 23, 2011

2.22.x

2.24.x

2.22.x

3.05.x

1.05.x

7.6

May 4, 2011

2.20.x

2.22.x

2.22.x  *)

3.03.x

1.03.x

7.5

Jan 10, 2011

2.18.x

2.20.x

2.18.x

n/a

n/a

7.4

Aug 10, 2010

2.16.x

2.05.x

n/a

n/a

n/a

7.3

Mar 2, 2010

2.12.x

2.04.x

n/a

n/a

n/a

7.2

Nov 17, 2009

2.09.x

2.04.x

n/a

n/a

n/a

7.1

Jun 18, 2009

2.06.x

2.03.x

n/a

n/a

n/a

7.0

Dec 23, 2008

2.03.11

n/a

n/a

n/a

n/a

*) For release 7.6, the repository version was 2.20.x for 7.6.3 and older.

**) For release 10.0, the Building a Website tutorial has replaced Go Green as reference implementation.

In general the HST is compatible with previous versions of the CMS.

For all available tags and releases, also see: