shaba/one
1
0
Fork 0
mirror of https://github.com/OpenNebula/one.git synced 2025-03-20 10:50:08 +03:00
Code Releases Wiki Activity

Links updated

Alberto P. Marti 2020-05-23 12:04:54 +02:00
parent 117f813ea4
commit 30f59396d2
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Release-Policy.md

@ -4,16 +4,16 @@ 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 **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.
* Each **major release** or **upgrade** of OpenNebula is denoted by a single major number, i.e. OpenNebula 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 OpenNebula is denoted by a major and a minor number, i.e. OpenNebula 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 OpenNebula is denoted by a major, a minor and an incremental number, i.e. OpenNebula 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">
</p>
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.
* **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 via our [Customer Portal](https://opennebula.pro) for Corporate Users with an active [OpenNebula Subscription](https://opennebula.io/enterprise/).
* **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:
@ -26,11 +26,10 @@ The OpenNebula project plans to release approximately:
<img align="center" src="https://github.com/OpenNebula/one/wiki/ONE_Dev_Cycle.png" width="400" >
</p>
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).
After the release of a new update (minor release) and during three months, we asynchronously release 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.
The software is thoroughly tested through a internal [quality assurance process](Quality-Assurance) before its release. We then prepare [packages of all releases for the most common Linux distributions](http://downloads.opennebula.io/packages/). During the entire life cycle, we make reasonable efforts to maintain compatibility for the core and data base across all minor and maintenance releases, but sometimes we have to make exceptions to this general compatibility goal due to critical impact or other significant issues.
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.
The open-source Project project can only provide community support and maintenance for the latest OpenNebula version. [OpenNebula Systems](http://opennebula.systems/) offers [commercial support subscriptions](http://opennebula.systems/opennebula-support/) for users that need support for previous versions and have access to the enterprise repository with hotfixes.
Users of any version of OpenNebula can obtain support from fellow users through our [Community Forum](https://forum.opennebula.io/). For **Corporate Users**, we offer a series of [Enterprise Services](https://opennebula.io/enterprise/), including **SLA-based support** for customers that need professional support for previous versions and want to enjoy access to **hotfix packages and other exclusive resources** via the [Customer Portal](https://opennebula.pro).