...
| Release Name | Status | Initial Release Date | Next Phase | EOL Date | |||
|---|---|---|---|---|---|---|---|
| New Delhi | Pre-Planning | 1H24 | Planning | TBD | |||
| Montreal | Pre-Planning | 2H23 | Planning | TBD | |||
| London | Pre-Planning | 1H23 | Planning | TBD | |||
| Kyoto | Pre-Planning | 2H22 | Planning | TBD | |||
| Jakarta | Pre-Planning | 1H22 | Planning | TBD | |||
| Istanbul | Pre-Planning | 2H21 | Planning | TBD | |||
| Honolulu | Pre-Planning | 1H21 | Planning | 2H21 | |||
| Guilin | Planning | 2H20 | Requirements Definition | 1H21 | |||
| Frankfurt | Development | 1H20 | Current Release | Current Release |
| Maintenance | TBD2H20 |
| El Alto | Current Release |
| EOLMaintenance | 1H20TBD | |||
| Dublin (doc) | EOL |
| 2H19 | ||||
| Casablanca (doc) | EOL |
|
| ||||
| Beijing (doc) | EOL |
|
| ||||
| Amsterdam (doc) | EOL |
|
|
...
| Status | Meaning |
|---|---|
| Pre-Planning | Only the release name has been determined. |
| Planning | Pre-M0. The release name has been chosen and tentative milestone dates have been determined. |
| Requirements Definition | Between M0 and M1. The schedule has been approved and requirements are being documented and prioritized. |
| Development | After M1 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. This release will be maintained until it is replaced by the next |
| Maintenance | The approved output of bug fixes and other changes made to the initial release. |
| End of Life (EOL) | This release has been replaced by a newer release and is no longer supported. |
...