add release related info for 'london'

Issue-ID: DOC-811

Signed-off-by: thmsdt <thomas.kulik@telekom.de>
Change-Id: Iea3b496496bbb9a9790d7f0408e7212c95d9ac02

1 files changed, 42 insertions, 33 deletions

diff --git a/docs/release/index.rst b/docs/release/index.rst
index 6a66071a1..2cdff466d 100644
--- a/docs/release/index.rst
+++ b/docs/release/index.rst
@@ -30,93 +30,105 @@ maintained in the component specific release notes.
 +-----------------------------------+-----------------------------------------+
 | **Release version**               | 12.0.0                                  |
 +-----------------------------------+-----------------------------------------+
-| **Release date**                  | 2023, not released yet                  |
+| **Release date**                  | 2023, July 6th                          |
 +-----------------------------------+-----------------------------------------+
 
 Features
 --------
-
 ONAP 'London' focusses on:
 
-- to be done
+- ONAP takeaways to get feedback from consumers on what we need to prioritize
+- ONAP evolution definition and mission statement refresh
+- Modularity and module bundles for specific use cases (O-RAN SMO, Network
+  slicing etc.)
+- Managing unmaintained projects
+- Formalizing ONAP as key player in open RAN @ O-RAN SC TOC Level
+- Getting first project: CPS road for gold badge
+- SBOMs delivery
+- Streamlining Release Management tasks
+- Implementing Service Mesh with ISTIO
+- Improving software quality by fixing bugs and upgrading components packages
+- First implementation of Java 17
+- Functional Requirements
 
-Functional Requirements
 -----------------------
 
 Richer Set of Cloud Native Functionality
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
 - to be done
 
 E2E Network Slicing
 ^^^^^^^^^^^^^^^^^^^
-
-- to be done
+Added support for 3GPP 28.532 based APIs in NSSMF for network slicing, with
+focus on RAN slicing.
 
 Control Loop Evolutions
 ^^^^^^^^^^^^^^^^^^^^^^^
-
-- to be done
+- Improvements to CLAMP Automation Composition Management (ACM).
+- Metadata driven API Generation.
+- Improved Metrics and SLAs.
+- Improved Testing.
 
 Extended O-RAN Integration
 ^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-- to be done
+- Enhancements for Configuration Management notification from O-RAN network
+  functions over O1 interface.
 
 Controllers
 ^^^^^^^^^^^
-
-- to be done
+- A1 policy and platform enhancements from CCSDK.
 
 Service Design
 ^^^^^^^^^^^^^^
-
-- to be done
+- Support for constraints.
+- UI support for view/edit/import data types.
+- Increased support for TOSCA functions.
+- Removed need for USER_ID cookie and header.
 
 Inventory
 ^^^^^^^^^
-
-- to be done
+- Addition of Cell and Neighbour objects.
 
 ONAP Operations Manager
 ^^^^^^^^^^^^^^^^^^^^^^^
-
-- to be done
+- Introduction of "Production" ONAP setup.
+- Removal of unsupported components (AAF, Portal, Contrib,...).
+- Update of component helm charts to use common templates and practices.
+- Introduction of Kubernetes Operators for Cassandra (k8ssandra-operator) - to
+  support latest Cassandra version (optional for London) and Keycloak.
 
 Non-Functional Requirements
 ---------------------------
-
 The following 'non-functional' requirements are followed in the
 'London' Release:
 
 Best Practice
 ^^^^^^^^^^^^^
-
 - to be done
 
 Security
 ^^^^^^^^
-
-- to be done
+- SBOMs generation.
+- Packages upgrades to limit number of affecting vulnerabilities.
 
 Documentation
 ^^^^^^^^^^^^^
-
-- to be done
+- Interactive architecture diagram updated
+- End-2-End guides removed because they have become outdated due to
+  unmaintained projects.
 
 Tests & Integration
 ^^^^^^^^^^^^^^^^^^^
-
-- to be done
+- Minor bug fixes, package upgrades and python version fixes.
+- Migration out of Orange infra and pipelines was started.
 
 <additional section to be added?>
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
 - to be done
 
 .. important::
-   Some non-functional requirements are not fully finalized. Please, check details
-   on the :doc:`Integration <onap-integration:usecases/release_non_functional_requirements>`
+  Some non-functional requirements are not fully finalized. Please, check details
+  on the :doc:`Integration <onap-integration:usecases/release_non_functional_requirements>`
 
 Documentation Sources
 ---------------------
@@ -130,9 +142,7 @@ community events.
 
 OpenSSF Best Practice
 ---------------------
-
 ONAP has adopted the `OpenSSF Best Practice Badge Program <https://bestpractices.coreinfrastructure.org/en>`_.
-
 - `Badging Requirements <https://github.com/coreinfrastructure/best-practices-badge>`_
 - `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
 
@@ -151,7 +161,6 @@ ONAP Maturity Testing Notes
 ---------------------------
 For the 'London' release, ONAP continues to improve in multiple areas of
 Scalability, Security, Stability and Performance (S3P) metrics.
-
 More details in :ref:`ONAP Integration Project<onap-integration:master_index>`
 
 Known Issues and Limitations