Ceph Releases

Current

Version

Initial release

Latest

End of life (estimated)

mimic

Jun 2018

13.2.4

luminous

Aug 2017

12.2.10

Timeline

Date

development

mimic

luminous

kraken

jewel

infernalis

hammer

giant

firefly

emperor

dumpling

Jan 2019

13.2.4

Jan 2019

13.2.3

Nov 2018

12.2.10

Nov 2018

12.2.9

Sep 2018

13.2.2

Sep 2018

12.2.8

Jul 2018

10.2.11

Jul 2018

13.2.1

Jul 2018

12.2.7

Jul 2018

12.2.6

Jun 2018

13.2.0

May 2018

13.1.0

Apr 2018

12.2.5

Apr 2018

13.0.2

Feb 2018

12.2.4

Feb 2018

12.2.3

Feb 2018

13.0.1

Dec 2017

12.2.2

Oct 2017

10.2.10

Sep 2017

12.2.1

Aug 2017

11.2.1

Aug 2017

12.2.0

Aug 2017

13.0.0

Aug 2017

12.1.4

Aug 2017

12.1.3

Aug 2017

12.1.2

Jul 2017

10.2.9

Jul 2017

10.2.8

Jul 2017

12.1.1

Jun 2017

12.1.0

May 2017

12.0.3

Apr 2017

10.2.7

Apr 2017

12.0.2

Mar 2017

10.2.6

Mar 2017

12.0.1

Feb 2017

0.94.10

Feb 2017

12.0.0

Jan 2017

11.2.0

Jan 2017

11.1.1

Dec 2016

10.2.5

Dec 2016

10.2.4

Dec 2016

11.1.0

Oct 2016

11.0.2

Oct 2016

11.0.1

Sep 2016

10.2.3

Aug 2016

0.94.9

Aug 2016

0.94.8

Jun 2016

10.2.2

Jun 2016

11.0.0

May 2016

10.2.1

May 2016

0.94.7

Apr 2016

10.2.0

Apr 2016

10.1.2

Apr 2016

10.1.1

Mar 2016

10.1.0

Mar 2016

10.0.5

Mar 2016

10.0.4

Feb 2016

9.2.1

Feb 2016

0.94.6

Feb 2016

10.0.3

Jan 2016

10.0.2

Dec 2015

10.0.1

Nov 2015

9.2.0

Nov 2015

0.80.11

Nov 2015

10.0.0

Oct 2015

0.94.5

Oct 2015

0.94.4

Oct 2015

9.1.0

Aug 2015

0.94.3

Aug 2015

9.0.3

Jul 2015

0.80.10

Jul 2015

9.0.2

Jun 2015

0.94.2

Jun 2015

9.0.1

May 2015

9.0.0

Apr 2015

0.87.2

Apr 2015

0.94.1

Apr 2015

0.94

Mar 2015

0.80.9

Feb 2015

0.87.1

Feb 2015

0.93

Feb 2015

0.92

Jan 2015

0.80.8

Jan 2015

0.91

Dec 2014

0.90

Dec 2014

0.89

Nov 2014

0.88

Oct 2014

0.87

Oct 2014

0.80.7

Oct 2014

0.80.6

Oct 2014

0.86

Sep 2014

0.67.11

Sep 2014

0.85

Aug 2014

0.67.10

Aug 2014

0.84

Jul 2014

0.80.5

Jul 2014

0.80.4

Jul 2014

0.80.3

Jul 2014

0.80.2

Jul 2014

0.83

Jun 2014

0.82

Jun 2014

0.81

May 2014

0.67.9

May 2014

0.67.8

May 2014

0.80.1

May 2014

0.80

Apr 2014

0.79

Mar 2014

0.78

Feb 2014

0.67.7

Feb 2014

0.67.6

Feb 2014

0.77

Jan 2014

0.76

Jan 2014

0.75

Dec 2013

0.67.5

Dec 2013

0.72.2

Dec 2013

0.74

Dec 2013

0.73

Nov 2013

0.72.1

Nov 2013

0.72

Oct 2013

0.67.4

Oct 2013

0.71

Oct 2013

0.70

Sep 2013

0.67.3

Sep 2013

0.69

Sep 2013

0.68

Aug 2013

0.67.2

Aug 2013

0.67.1

Aug 2013

0.67

Understanding the release cycle

There is a new stable release cycle every nine (9) months, starting after the Luminous release (12.2.0). Each stable release series will receive a name (e.g., ‘Mimic’) and a major release number (e.g., 13 for Mimic because ‘M’ is the 13th letter of the alphabet).

Releases are named after a species of cephalopod (usually the common name, since the latin names are harder to remember or pronounce).

Version numbers have three components, x.y.z. x identifies the release cycle (e.g., 13 for Mimic). y identifies the release type:

  • x.0.z - development releases (for early testers and the brave at heart)

  • x.1.z - release candidates (for test clusters, brave users)

  • x.2.z - stable/bugfix releases (for users)

This versioning convention started with the 9.y.z Infernalis cycle. Prior to that, versions looked with 0.y for development releases and 0.y.z for stable series.

Development releases (x.0.z)

Each development release (x.0.z) freezes the master development branch and applies integration and upgrade tests before it is released. Once released, there is no effort to backport fixes; developer focus is on the next development release which is usually only a few weeks away.

  • Development release every 4 to 8 weeks

  • Intended for testing, not production deployments

  • Full integration testing

  • Upgrade testing from the last stable release(s)

  • Every effort is made to allow offline upgrades from previous development releases (meaning you can stop all daemons, upgrade, and restart). No attempt is made to support online rolling upgrades between development releases. This facilitates deployment of development releases on non-production test clusters without repopulating them with data.

Release candidates (x.1.z)

There is a feature release roughly six (6) weeks prior to the planned initial stable release, after which focus shifts to stabilization and bug fixes only.

  • Release candidate release every 1-2 weeks

  • Intended for final testing and validation of the upcoming stable release

Stable releases (x.2.z)

Once the initial stable release is made (x.2.0), there are semi-regular bug-fix point releases with bug fixes and (occasionally) small feature backports. Bug fixes are accumulated and included in the next point release.

  • Stable point release every 4 to 6 weeks

  • Intended for production deployments

  • Bug fix backports for two full release cycles.

  • Online, rolling upgrade support and testing from the last two (2) stable release(s) (starting from Luminous).

  • Online, rolling upgrade support and testing from prior stable point releases

For each stable release:

In the timeline above, the life time of a stable release series is calculated to be approximately 18 months (i.e., two 9 month release cycles) after the month of the first release. For example, Luminous (12.2.z) will reach end of life (EOL) shortly after Nautilus (14.2.0) is released. The lifetime of a release may vary because it depends on how quickly the stable releases are published.

The life time for Jewel and Kraken are slightly different. Prior to Luminous, only every other stable release was an “LTS” release. Therefore,

  • Upgrades are supported from Jewel -> Kraken -> Luminous and Jewel -> Luminous.

  • Upgrades from Jewel or Kraken must upgrade to Luminous first before proceeding further (e.g., Kraken -> Luminous -> Mimic but not Kraken -> Mimic).

  • Jewel will be maintained until Mimic is released in the spring of 2018.

  • Kraken is no longer maintained.