Release Name | Current Phase | Release Date | Next Phase | Timeline | RSAC requirements at release start |
|---|---|---|---|---|---|
| K Release | Planning | Dec 2024 | Requirements definition | timeline | |
| J Release | Requirements definition | Jun 2024 | Development | timeline | |
| I Release | Current release | Dec 2023 | EOL | timeline | |
| H Release | EOL | Jun 2023 | EOL | timeline | |
| G Release | EOL | Dec 2022 | EOL | timeline | |
| F release | EOL | Jun 2022 | EOL | timeline | link |
| E release | EOL |
| EOL | timeline | link |
| D Release | EOL |
| EOL | timeline | link |
| Cherry | EOL |
| EOL | timeline | link |
| Bronze | EOL |
| EOL | timeline | link |
| Amber | EOL |
| EOL | not available |
Status Definitions:
Status | Meaning | |
|---|---|---|
| 1 | Planning | Pre-M0. The release name has been chosen and tentative milestone dates have been determined. |
| 2 | Requirements definition | Between M0 and M1. Timeline is approved. Epics and User Stories are labeled with the release names and entered into jira. |
| 3 | Development | After M1 and before release. Code development for sprints updated in jira. |
| 4 | 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 release. |
| 5 | End of life (EOL) | Release is complete. |
Status Definitions:
Status | Meaning | |
|---|---|---|
| 1 | Planning | Pre-M0. The release name has been chosen and tentative milestone dates have been determined. |
| 2 | Requirements definition | Between M0 and M1. Timeline is approved. Epics and User Stories are labeled with the release names and entered into jira. |
| 3 | Development | After M1 and before release. Code development for sprints updated in jira. |
| 4 | 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 release. |
| 5 | End of life (EOL) | Release is complete. |
7 Comments
Madan Cheemakurthi
The release date for "Cherry" is given as 12th December 2020 and the Cherry Release Revised Sprint Calendar 2020 also shows that the Cherry release is in the week of 8th-12th December 2020. But the "Current Phase" of Cherry Release is being shown above in the Release Timelines table as "Requirements Definition" and the Next Phase as "Development".
I am more surprised by this page's update time
"Created by Farheen Cefalu, last modified by Rittwik Jana on Mar 03, 2021"
Is this a typo? Or there is still active development to be done for Cherry Release?
Is Cherry Release done or not?
Thoralf Czichy
cherry is done. I updated this wiki page accordingly.
Animesh Verma
Hi Thoralf Czichy Can you please guide me on how to debug subscription managers and rtmgr services other than building and running them on the Kubernetes cluster every time.
Is there a way to do local development
Thoralf Czichy
I know that some developers did this in the past. So it's - obviously - technically possible. However, you'd have to modify build scripts accordingly. The Dockerfiles usually assume Ubuntu 20.04 as build image. I doubt that there are any dependency conflicts between the submgr and rtmgr if you use a plain Ubuntu installation as starting point. If you have this working, I'd be happy to see this as contribution.
Animesh Verma
Hi Thoralf Czichy , So I am halfway towards running services in local environment for Development and Debugging purpose by editing the Docker files. I think I can get the setup done soon.
Great to hear this can be considered as a contribution. Looking forward to connecting with you on this.
Was trying my luck if we already had some local development system present.
Thanks for the Help.
Zhengwei Gao
Is D release done or not? The timeline is outdated.
Brand Lu
For the SPEC file, what's the mapping for different Release, such as O-RAN.WG10.O1-Interface.0-v06.00 this interface document is mapping with which release?