shaba/one
1
0
Fork 0
mirror of https://github.com/OpenNebula/one.git synced 2025-01-06 13:17:42 +03:00
Code Releases Wiki Activity

Updated Release Policy (markdown)

Ignacio M. Llorente 2019-04-22 14:54:20 -04:00
parent a2955d7e41
commit e541a7ebb8
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Release-Policy.md

@ -14,8 +14,7 @@ Incremental releases can be **maintenance public** or **hotfix private** release
* **Hotfix private** – Incremental update to fix specific issues. Although all code in OpenNebula is fully open, packages from hotfix incremental versions are not publicly released, and are only available for users with an active commercial subscription.
* **Maintenance public** – Incremental update between minor/major releases to fix multiple outstanding issues. Both code and packages are publicly available.
![ReleaseCycle](https://github.com/OpenNebula/one/wiki/ONE_Release_Cycle.png "")
![ReleaseCycle](http://opennebula.org/wp-content/uploads/2013/12/opennebulareleases2.png "")
The OpenNebula project plans to release approximately:
* A new **upgrade** (major) version of OpenNebula approximately every 3-5 years.
@ -23,11 +22,12 @@ The OpenNebula project plans to release approximately:
* 1 **maintenance** (incremental) version for each minor version. There is at least one maintenance release between two consecutive minor releases.
* Several **hotfix** (incremental) versions for critical impact issues with a frequency of weeks for each minor version.
![ReleaseCycle2](http://opennebula.org/wp-content/uploads/2013/12/ONE_Dev_Cycle.png "")
After the release of a new update (minor release) and during three months, the Project asynchronously releases hotfixes with critical bug fixes for the previous update version to allow time to update to the latest version. This period is extended to six months when the new version is an upgrade (major version).
Four weeks before an official major or minor release date, there is a **beta release** series. This beta series marks the feature-freeze for the release, development efforts are then mainly devoted to bug fixing and polishing.
![ReleaseCycle2](http://opennebula.org/wp-content/uploads/2013/12/opennebulareleases2.png "")
The software is thoroughly tested through a internal [quality assurance process](Quality-Assurance) before its release. The OpenNebula project prepares [packages of all releases for the most common linux distributions](http://downloads.opennebula.org/packages/). 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.