G release plan (<date>):

• New HW-Rust xApp to support RUST framework
• HW(python) - RIC Subscription using python xApp framework 
• RC xApp - GRPC interface support on RC xApp
• Bouncer xApp - RIC Benchmarking new features addition
• KPIMON-GO xApp – Version 2.0
• AD & QP xApp – InfluxDB database integration to fetch data.

G release highlights/accomplishments (<date>):

G release source code, container images and deployment instructions

Code Coverage Reports : Latest reports can be found at the following Link: Projects - O-RAN Software Community (sonarcloud.io).

Mission: TODO

Original primary goals:

• E2T improvements: Support for E2 Reset procedure (from E2 node to RIC (RIC-386); Correct handling of E2 node reconnects and multiple E2 Setups (RIC-932), Support split architecture (CU/DU) in E2T/E2M.
  
• A1: finalize re-implementation of A1 in golang (from python)
• Remove support for RMR in E2 subscription interface and only continue with E2 REST subscription interface towards xApps
  • can be done because last missing xapp-framwork supports REST (xapp-frame-cpp). Go and python already support E2 REST subscriptions
• Subscription delete callback to xApps and subscription cleanup after xApp removal.
• Support for DMS via REST in addition to command line tool DMSCLI
• First version of the xApp framework for Rust
• First version of a RIC CLI

Achieved G release highlights = high-level release notes (2022-05-18) below (note that the release image list is here: TODO)

• TODO

For the G release of the near-RT RIC we do only limited integration testing: only the use cases: deploy RIC, deploy xApp and make E2 connection are to be tested.

Filled in end-of-release checklist : Release criteria checklist - TODO

Status 2022-06-21: list of committed items: link

G release source code, container images and deployment instructions

Primary Goals:

According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.

G release Feature Scope: 

• • support of O-RAN WG10 VES message bodies
  • update of OAM-Controller to ODL version Sulfur
    • Note: team decided to go with Java11 - Java 17 would be possible but is pushed out to next release.
  • update to keycloak version 18
  • even more secure keycloak configuration
  • there is a request for a "bare-metal" deployment which is not in scope of O-RAN, but still useful - also for development and module test
  • support of AI/ML based on RSAC and other input.
  • support of Tacker team

Please see also project wiki for further details: G-Release

Primary Goals:

G release Feature Scope: 

Primary Goals:

G release Feature Scope: 

Primary Goals:

• Keep alignment with latest O-RAN specifications (O1, E2)

G Feature Scope / Achievements:

• keep alignment of the O1 Simulator with latest YANG models
• E2 Simulator improvements (especially to the deployment/build procedures)
• NS3-E2 Simulator integration in Gerrit

G release source code, container images and deployment instructions

Source code: TODO

Container images are described here: TODO

Instructions:TODO

Code coverage: in progress (sonar for C/C++ code in LF repos)

Primary Goals:

The SMO acts as an uber identity that overlooks the different aspects of the O-RAN deployment. Starting with how solutions are deployed, to how they interact with each other, to how they are managed.

G release Feature Scope: 

The focus for the G release in SMO is interoperability. Every sub-project within SMO has at least one item that focuses on interoperating with one other entity outside of SMO. For example,

• On the O1 interface, the focus is on trying to bring-up O-DU using NETCONF and YANG models defined for O-DU.
• On the O1/VES interface, it is ability to generate network slicing PM events in the O-DU, and the ability to receive them in SMO dashboard, and store them in InfluxdB.
• On the O2 interface, it will be the ability to instantiate an instance of a Network Function (NF) like the O-DU in the O-Cloud.

Separate from this, each sub-project within SMO has other features/capabilities it will address as part of the G-release. For details please refer to the minutes of the SMO meeting here.