...
Release Name | Status | Most Recent Maintenance Release Date | Initial Release Date | Next Phase | EOL Date | ||
---|---|---|---|---|---|---|---|
Rabat | Pre-Planning | TBD | 1H26 | Planning | TBD | ||
QuebecNew Delhi | Pre-Planning | TBD | 1H242H25 | Planning | TBD | ||
MontrealParis | Pre-Planning | TBD | 2H231H25 | Planning | TBD | ||
LondonOslo | Pre-Planning | TBD | 1H232H24 | Planning | TBD | ||
KohnNew Delhi | Pre-Planning | TBD | 2H221H24 | Planning | TBD | ||
JakartaMontreal | Development | TBD | 1H222H23 | Current Release | TBD | ||
IstanbulLondon | Current Release |
| Supported Release | 1H24 | |||
Kohn | Supported Release |
| EOL | 2H23 | |||
Jakarta | EOL |
|
| ||||
Istanbul | EOL |
|
| Maintenance Release | 1H22 |
| |
Honolulu | EOL |
|
|
| |||
Guilin | EOL |
|
|
| |||
Frankfurt | EOL |
|
|
| |||
El Alto | EOL |
|
|
| |||
Dublin (doc) | EOL |
|
| ||||
Casablanca (doc) | EOL |
|
|
| |||
Beijing (doc) | EOL |
|
| ||||
Amsterdam (doc) | EOL |
|
|
...
Status | Meaning |
---|---|
Pre-Planning | Only the release name and an approximate time frame hav have been determined. |
Planning | Pre-M0. The release name has been chosen and tentative milestone dates have been determined. |
Requirements Definition | Between M0 and M2. The schedule has been approved and requirements are being documented and prioritized. |
Development | After M2 but before release. Requirements are being implemented and tested. |
Current Release | The approved output of the release process which interested end users should be deploying. |
Maintenance Release | The approved output of bug fixes and other changes made to the initial release, or a prior maintenance release. |
Supported Release | Previously a Current Release. Still supported, but only receiving critical updates. ONAP supports the current release and the current release - 1. |
End of Life (EOL) | This release is no longer supported. |
...