This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
software:release [2013/12/02 14:06] – tinova | software:release [2014/01/07 15:27] (current) – jfontan | ||
---|---|---|---|
Line 1: | Line 1: | ||
~~NOTOC~~ | ~~NOTOC~~ | ||
- | < | + | < |
- | ====== Release Schedule ====== | + | |
- | + | ||
- | The following table shows the release date of past and future versions of OpenNebula. | + | |
- | + | ||
- | < | + | |
+ | < | ||
^ Version ^ Date ^ Release Notes ^ Type ^ | ^ Version ^ Date ^ Release Notes ^ Type ^ | ||
|4.4 | Dec, 3 2013| [[.: | |4.4 | Dec, 3 2013| [[.: | ||
Line 67: | Line 63: | ||
|TP 2| June 17, 2008|[[.: | |TP 2| June 17, 2008|[[.: | ||
|TP 1| March 26, 2008|[[.: | |TP 1| March 26, 2008|[[.: | ||
+ | |||
+ | < | ||
< | < | ||
Line 103: | Line 101: | ||
</ | </ | ||
- | //(*) OpenNebula is truly open-source software, all source code is publicly available in our [[http:// | ||
- | ====== 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, | ||
- | * Each **maintenance or incremental release** of ONE is denoted by a major, a minor and an incremental number, i.e.: ONE 2.2.1. | ||
- | |||
- | {{ : | ||
- | |||
- | 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. | ||
- | |||
- | {{ : | ||
- | |||
- | |||
- | The software is thoroughly tested through a [[http:// | ||
- | The OpenNebula project can only provide community support and maintenance for the last minor (update) version. If you want a longer time support, [[http:// |