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:55:32 -04:00
parent e541a7ebb8
commit a178306a74
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

@ -10,19 +10,19 @@ OpenNebula follows a rapid release cycle to improve user satisfaction by rapidly
* Each **update** or **minor release** of ONE is denoted by a major and a minor number, i.e.: ONE 5.8. 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 update process for production environments following a pre-defined migration path.
* Each **incremental release** of ONE is denoted by a major, a minor and an incremental number, i.e.: ONE 5.8.1. A new incremental release typically only includes bug fixes and minor enhancements.
![ReleaseCycle](https://github.com/OpenNebula/one/wiki/Release-Policy/ONE_Release_Cycle.png "")
Incremental releases can be **maintenance public** or **hotfix private** releases.
* **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](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.
* 6-10 **update** (minor) versions for each major version. There is an OpenNebula major or minor release approximately every 6 months.
* 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 "")
![ReleaseCycle](https://github.com/OpenNebula/one/wiki/Release-Policy/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).