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 2020-07-16 19:21:05 +02:00
parent a31c881df4
commit e0806735b7
1 changed files with 0 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
Release-Policy.md

@ -72,41 +72,4 @@ Once the QA process is completed, we prepare [packages of all releases](http://d
Users of OpenNebula Community Edition can obtain support from fellow users through our [Community Forum](https://forum.opennebula.io/). Corporate Users with an active [OpenNebula Subscription](https://opennebula.io/enterprise/) have access not only to the **Enterprise Edition** and its **private maintenance releases**, but also to exclusive** Enterprise Tools** and **technical contents**, **SLA-based support **and **Professional Services** via the [Customer Portal](https://support.opennebula.pro/).
****
OpenNebula releases two software versions:
* **Community Edition (CE)**: a fully-featured version of OpenNebula that is publicly released.
* **Enterprise Edition (EE)**: a more tested, hardened, and production-ready version of OpenNebula for enterprise use that incorporates additional bug fixes developed by OpenNebula Systems and software patches with minor enhancements. The Enterprise Edition is a private version only available via our [Customer Portal](https://support.opennebula.pro/) for Corporate Users with an active [OpenNebula Subscription](https://opennebula.io/enterprise/). Customers also have access to exclusive Enterprise Tools to simplify upgrades and the maintenance of OpenNebula clouds in production environments.
OpenNebula publishes major, minor and maintenance releases:
* Each **major release** of OpenNebula is denoted by a single major number (i.e. OpenNebula 5). A new major release typically comes with significant additions that may involve changes in the interfaces, core or database, and so may require a complex upgrade process for production environments.
* Each **minor release** of OpenNebula is denoted by a major and a minor number (i.e. OpenNebula 5.12). A new minor release typically involves enhancements, optimizations and bug fixes that may bring along small changes in the core and database, and so allow a seamless update process for production environments following a pre-defined migration path.
* **Maintenance releases** of OpenNebula are denoted depending on whether they apply to the Community Edition (i.e. OpenNebula 5.12.0.x) or to the Enterprise Edition (i.e. OpenNebula 5.12.x). A maintenance release typically includes only bug fixes and minor enhancements, and its upgrade is straightforward.
<p align="center">
<img src="https://github.com/OpenNebula/one/wiki/ONE_Release_Cycle.png" width="550">
</p>
In major and minor releases, both editions share the same numbering—so, for example, OpenNebula 5.12 is distributed in both editions. However, maintenance releases follow a different versioning:
* **Enterprise maintenance** releases are denoted by _major_._minor_._maintenance_ (i.e. 5.12.1)
* **Community maintenance** releases are denoted by _major_._minor_.0._maintenance_ (i.e. 5.12.0.1)
For each new major or minor release, OpenNebula Systems contributes to the Community Edition all bug fixes and software patches with minor enhancements that have been developed and incorporated into an Enterprise Edition version during the previous maintenance cycle.
We plan to produce approximately:
* A new **major release** of OpenNebula approximately every 3-5 years.
* 6-10 **minor releases** for each major version. There is an OpenNebula major or minor release approximately every 6 months.
* At least one **public maintenance release** for each minor Community Edition release.
* Several **private maintenance releases** for each Enterprise Edition release, with a frequency of weeks.
<p align="center">
<img align="center" src="https://github.com/OpenNebula/one/wiki/ONE_Dev_Cycle.png" width="400" >
</p>
After producing a new minor release, and for a period of three months, we asynchronously publish **Enterprise maintenance releases** with critical bug fixes for the previous minor version to allow time to upgrade to the latest version. This period is extended to six months when the new version is a major release.
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. A **Release Candidate** version is usually published one week before an official major or minor release date.