Ceph Releases

Timeline

  Luminous Kraken EOL Jewel Infernalis EOL Hammer EOL Giant EOL Firefly EOL Emperor EOL Dumpling EOL
First release August 2017 January 2017 April 2016 November 2015 April 2015 October 2014 May 2014 November 2013 August 2013
Estimated retirement   August 2017 June 2018   May 2017   January 2016   March 2015
Actual retirement   August 2017   April 2016 August 2017 April 2015 April 2016 May 2014 May 2015
  Development Luminous Kraken Jewel Infernalis Hammer Giant Firefly Emperor Dumpling
October 2017       10.2.10            
September 2017   12.2.1                
August 2017 12.1.4 12.2.0 11.2.1              
12.1.3                  
12.1.2                  
July 2017 12.1.1     10.2.9            
      10.2.8            
June 2017 12.1.0                  
May 2017 12.0.3                  
April 2017 12.0.2     10.2.7            
March 2017 12.0.1     10.2.6            
February 2017 12.0.0         0.94.10        
January 2017 11.1.1   11.2.0              
December 2016 11.1.0     10.2.5            
      10.2.4            
October 2016 11.0.2                  
11.0.1                  
September 2016       10.2.3            
August 2016           0.94.9        
          0.94.8        
June 2016 11.0.0     10.2.2            
May 2016       10.2.1   0.94.7        
April 2016 10.1.2     10.2.0            
10.1.1                  
March 2016 10.1.0                  
10.0.5                  
February 2016 10.0.3       9.2.1 0.94.6        
January 2016 10.0.2                  
December 2015 10.0.1                  
November 2015 10.0.0       9.2.0     0.80.11    
October 2015 9.1.0         0.94.5        
          0.94.4        
August 2015 9.0.3         0.94.3        
July 2015 9.0.2             0.80.10    
June 2015 9.0.1         0.94.2        
May 2015 9.0.0                  
April 2015           0.94.1 0.87.2      
          0.94        
March 2015               0.80.9    
February 2015 0.93         0.87.1 0.87.1      
0.92                  
January 2015 0.91             0.80.8    
December 2014 0.90                  
0.89                  
November 2014 0.88                  
October 2014 0.86           0.87 0.80.7    
              0.80.6    
September 2014 0.85                 0.67.11
August 2014 0.84                 0.67.10
July 2014 0.83             0.80.5    
              0.80.4    
              0.80.3    
              0.80.2    
June 2014 0.82                  
0.81                  
May 2014               0.80.1   0.67.9
              0.80   0.67.8
April 2014 0.79                  
March 2014 0.78                  
February 2014 0.77                 0.67.7
                  0.67.6
January 2014 0.76                  
0.75                  
December 2013 0.74               0.72.2 0.67.5
0.73                  
November 2013                 0.72.1  
                0.72  
October 2013 0.71                 0.67.4
0.70                  
September 2013 0.69                  
0.68                 0.67.3
August 2013                   0.67.2
                    0.67.1
                  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.