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 terminology for major/minor releases

Alberto P. Marti 2020-01-02 18:57:08 +01:00
parent f56b8fba5c
commit 5f9f76b661
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Release-Policy.md

@ -4,9 +4,9 @@ The OpenNebula project publishes this Release Cycle Policy in an effort to provi
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 5. 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 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.
* Each **major release** or **upgrade** of ONE is denoted by a single major number, i.e.: ONE 5. 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 **minor release** or **update** 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 includes only bug fixes and minor enhancements.
<p align="center">
<img src="https://github.com/OpenNebula/one/wiki/ONE_Release_Cycle.png" width="550">
@ -17,10 +17,10 @@ Incremental releases can be **maintenance public** or **hotfix private** release
* **Maintenance public** – Incremental update between minor/major releases to fix multiple outstanding issues. Both code and packages are publicly available.
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.
* A new **major release** (upgrade) of OpenNebula approximately every 3-5 years.
* 6-10 **minor releases** (update) for each major version. There is an OpenNebula major or minor release approximately every 6 months.
* 1 **maintenance release** (incremental) for each minor version. There is at least one maintenance release between two consecutive minor releases.
* Several **hotfix releases** (incremental) for critical impact issues with a frequency of weeks for each minor version.
<p align="center">
<img align="center" src="https://github.com/OpenNebula/one/wiki/ONE_Dev_Cycle.png" width="400" >