Release Cycle

Release Schedule

The following table shows the release date of past and future versions of OpenNebula.

Version Date Release Notes Type
4.8.0 August, 12th 2014 Release Notes Update
4.7.80 July, 21st 2014 Release Notes Development
4.6.2 Jun, 12th 2014 Release Notes Maintenance
4.6.1 May, 21st 2014 Release Notes Maintenance
4.6 April, 29th 2014 Release Notes Update
4.6 RC April, 11th 2014 Release Notes Development
4.6 Beta March, 17th 2014 Release Notes Development
4.4.1 Feb, 4 2014 Release Notes Maintenance
4.4 Dec, 3 2013 Release Notes Update
4.4 RC November, 22 2013 Incremental Release Notes Development
4.4 Beta 2 November, 18 2013 Incremental Release Notes Development
4.4 Beta November, 7 2013 Release Notes Development
3 SP2 (3.8.5) October 25, 2013 Incremental Release Notes Maintenance
4.2 July 26, 2013 Release Notes Update
4.2 Beta July, 19 2013 Release Notes Development
3 SP1 (3.8.4) June, 18 2013 Incremental Release Notes Maintenance
4.0.1 May, 20 2013 Incremental Release Notes Maintenance
4.0 May, 8 2013 Release Notes Upgrade
4.0 RC April, 18 2013 Incremental Release Notes Development
4.0 Beta March, 26 2013 Release Notes Development
3.8.3 January 11, 2013 Incremental Release Notes Maintenance
3.8.2 November 8, 2012 Incremental Release Notes Maintenance (*)
3.8.1 October 26, 2012 Incremental Release Notes Maintenance
3.8 October 22, 2012 Release Notes Update
3.8 Beta October 9, 2012 Release Notes Development
3.6.3 October 30, 2012 Incremental Release Notes Maintenance (*)
3.6.2 August 30, 2012 Incremental Release Notes Maintenance (*)
3.6.1 May 3, 2012 Incremental Release Notes Maintenance (*)
3.6 July 10, 2012 Release Notes Update
3.6 Beta June 25, 2012 Release Notes Development
3.4.4 July 13, 2012 Incremental Release Notes Maintenance (*)
3.4.3 June 11, 2012 Incremental Release Notes Maintenance (*)
3.4.2 May 7, 2012 Incremental Release Notes Maintenance (*)
3.4.1 May 3, 2012 Incremental Release Notes Maintenance
3.4 April 11, 2012 Release Notes Update
3.4 Beta March 30, 2012 Release Notes Development
3.4 – S0 February 21, 2012 Release Notes Development
3.2.2 April 12, 2012 Incremental Release Notes Maintenance (*)
3.2.1 January 30, 2012 Incremental Release Notes Maintenance
3.2 January 17, 2012 Release Notes Update
3.2 RC December 23, 2011 Release Notes Development
3.2 Beta December 16, 2011 Incremental Release Notes Development
3.2 – S0 + S1 November 18, 2011 Release Notes Development
3.0 October 3, 2011 Release Notes Upgrade
3.0 RC1 September 23, 2011 Incremental Release Notes Development
3.0 (Beta2) September 8, 2011 Incremental Release Notes Development
3.0 (Beta) July 20, 2011 Release Notes Development
2.2.1 Jun 9th, 2011 Incremental Release Notes Maintenance
2.2 March 29, 2011 Release Notes Update
2.2 RC1 March 20, 2011 Incremental Release Notes Development
2.2 (Beta) March 2, 2011 Release Notes Development
2.0.1 December 3, 2010 Incremental Release Notes Maintenance
2.0 October 25, 2010 Release Notes Upgrade
2.0 RC1 September 23, 2010 Release Notes Development
2.0 (Beta1) July 17, 2010 Release Notes Development
1.4 December 16, 2009 Release Notes Update
1.4 RC November 18, 2009 Release Notes Development
1.4 (Beta2) October 30, 2009 Release Notes Development
1.2.1 July 29, 2009 Incremental Release Notes Maintenance
1.4 (Beta1) July 23, 2009 Development
1.2 February 6, 2009 Release Notes Update
1.2 (Beta2) January 12, 2009 Development
1.2 (Beta1) November 30, 2008 Development
1.0 July 24, 2008 Release Notes Upgrade
TP 2 June 17, 2008 Incremental Release Notes Development
TP 1 March 26, 2008 Release Notes Development

(*) OpenNebula is truly open-source software, all source code is publicly available in our repository and all software packages are available for most common Linux distributions. Before OpenNebula 3.8, some Maintenance Releases were only available for commercial subscribers.

Release Cycle Policy

The OpenNebula project publishes this Release Cycle Policy in an effort to provide as much transparency as possible and may make exceptions as necessary.

OpenNebula follows a rapid release cycle to improve user satisfaction by rapidly delivering features and innovations based on user requirements and feedback. In other words, giving customers what they want more quickly, in smaller increments, while additionally increasing technical quality.

  • Each upgrade or major release of ONE is denoted by a single major number, i.e.: ONE 2. A new major release typically means significant changes that may involve changes in the interfaces, core and data base and so may require a complex upgrade process for production environments.
  • Each update or minor release of ONE is denoted by a major and a minor number, i.e.: ONE 2.2. A new minor release typically signifies enhancements, optimizations and bug fixes that may involve small changes in the core and data base and so allow a seamless upgrade process for production environments following a pre-defined migration path.
  • Each maintenance or incremental release of ONE is denoted by a major, a minor and an incremental number, i.e.: ONE 2.2.1. A new maintenance release typically only includes bug fixes and minor enhancements.

opennebulareleases

The OpenNebula project plans to release:

  • A new upgrade (major release) of OpenNebula approximately every year and to provide two or three updates (minor release) for each major version. This means that there is an OpenNebula release every three or four months.
  • Additionally there are four maintenance releases every year, one between two consecutive major or minor releases. The Project may asynchronously distribute maintenance releases for critical impact issues.
  • After its first year, and for two additional years, the Project distributes a service pack (SP) for each major release that combines all the patches to easily install or deploy its last update.
  • Prior to an official major or minor release date there is a beta release two weeks before. This beta release marks the feature-freeze for the release and development efforts are then mainly devoted to bug fixing and polishing.

opennebulareleases2

The software is thoroughly tested through a internal quality assurance process before its release. The OpenNebula project prepares packages of all releases for the most common linux distributions. During the entire life cycle, the Project makes reasonable efforts to maintain compatibility for the core and data base across all minor and maintenance releases. The Project may elect to make exceptions to the compatibility goal for critical impact or other significant issues.

The OpenNebula project can only provide community support and maintenance for the last minor (update) version. If you want a longer time support, C12G Labs provides support and maintenance during 5 year periods for each of the major releases of OpenNebula.