update release note

Issue-ID: DOC-826

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

diff --git a/docs/release/index.rst b/docs/release/index.rst
index 358ccfe..ab1ac4f 100644 (file)
--- a/docs/release/index.rst
+++ b/docs/release/index.rst
@@ -8,7 +8,7 @@
 'Oslo' Release Notes
 ====================
 
 'Oslo' Release Notes
 ====================
 

-This page provides the release notes for the ONAP 'Oslo' release. This
+This page provides the release notes for the latest ONAP release. This

 includes details of software versions, known limitations, and outstanding
 trouble reports.
 
 includes details of software versions, known limitations, and outstanding
 trouble reports.
 


@@ -33,78 +33,51 @@ maintained in the component specific release notes.
 | **Release date**                  | 2025, January 16th                      |
 +-----------------------------------+-----------------------------------------+
 
 | **Release date**                  | 2025, January 16th                      |
 +-----------------------------------+-----------------------------------------+
 

-=== TO BE UPDATED ===
+ONAP is a comprehensive collection of Network Automation functions, including
+orchestration, management, and automation of network and edge computing
+services for network operators, cloud providers, and enterprises.
+
+The ONAP Oslo release continues the ONAP Streamlining evolution, advancing
+individual ONAP components and clusters, enhancing security, modernizing
+environments, and supporting intent-based declarative solutions and GenAI
+capabilities.
+
+The Oslo key features as follows:
+
+- **Security Enhancements**: ONAP projects have addressed critical security
+  concerns by converting ports to HTTPS, removing hard-coded passwords,
+  enabling Kubernetes pods to operate with non-root privileges, and mitigating
+  Common Vulnerabilities and Exposures (CVEs). These measures have
+  significantly bolstered the platform’s security. Additionally, by leveraging
+  industry-standard/de facto security protocol and mechanisms such as
+  Istio Service Mesh and Ingress Gateway, ONAP ensures secure inter- and
+  intra-component communications.
+- **Platform Modernization**: Components such as the Common Controller Software
+  Development Kit (CCSDK), Configuration Persistence Service (CPS), 
+  Usecase User Interface (UUI), Portal-NG and Policy Framework were upgraded
+  to Java 17. Additionally, various software versions updates ensure that ONAP
+  leverages the latest software development frameworks.
+- **ONAP Streamlining Evolution**: This initiative makes ONAP components
+  modular and independent through interface abstraction, loose coupling and
+  CI/CD. As a result, ONAP has evolved into a collection of individual network
+  orchestration functions, allowing the industry to pick and choose specific
+  components and enabling flexible and dynamic function adoption.
+- **Intent-based Declarative and GenAI Solutions**: Supports generative AI
+  solutions powered by large language models (LLMs), and includes data service
+  enhancements (domain-specific datasets) of Intent-driven networks and
+  Model-As-A-Service (MAAS).
+- **Industry Standard-Based Network Interface Upgrade**: CCSDK/SDNC now
+  supports an RFC8040-compliant network interface.
+- **OpenSSF Gold Standard Achievement**: The CPS and Policy Framework projects
+  have achieved the Open Source Security Foundation (OpenSSF) Gold Badging
+  standard, demonstrating ONAP’s commitment to high-quality, secure, and
+  reliable open-source software development.

 
 

-ONAP is evolving. We took efforts in streamlining processes and roles and
-NewDelhi release is the first one with agreed simplified software development
-life cycle governance.
-
-OpenSSF Gold Standard
----------------------
-
-We are proud to announce that first ONAP project achieved OpenSSF Gold
-standard. It will give ONAP consumers great confidence in the quality,
-security, and reliability of CPS.
-
-Java 17
--------
-
-First ONAP projects (CCSDK, CPS, UUI and Policy) completed their upgrades to
-Java 17. Spring boot (uplift to v3.1.2) and OpenApi 3 upgrades were also
-performed. These upgrades allow benefits of patched vulnerabilities and
-software efficiencies in the latest versions.
-
-CPS
----
-
-ONAP CPS project continued efforts in improvement of read/write, query
-operations, and huge reduction of memory consumption allowing for improved
-query performance and improve stability.
-
-Modeling
---------
-
-Modeling project added provision of YANG modules automation tools, which helps
-improve the YANG development efficiency and check the version update of the
-YANG model.
-
-OOM
----
-
-OOM project team added support for Gateway-API in Ingress template (13.0.1) as
-well as support for mariadb-operator (13.0.2). All ONAP MariaDB instances will
-now be created with the latest version by default using the mariaDB-operator.
-Added Galera clients (e.g. SO, SDNC) will use access to "primary" pod to avoid
-"Deadlocks". Additionally added default role creation to ServiceAccount for
-better access management.
-
-SDC
----
-
-SDC implemented-services update capability directly in yaml was added, more
-comprehensive support for defining behavior of interface operations and
-adaptability to define CSAR structure and content to suit the requirements of
-individual models.
-
-CCSDK
------
-
-CCSDK continued maintaining alignment with OpenDaylight release schedule by
-upgrading to OpenDaylight Argon version, Service Release 2. This allows latest
-ONAP user to make use of latest OpenDaylight software when they use latest
-release of ONAP.
-
-Portal-NG
----------
-
-We introduced new Portal-NG as a maintained alternative to the unmaintained
-Portal project.  Allows ONAP user to make informed decisions on software use of
-maintained and unmaintained projects.

 
 Documentation Sources
 ---------------------
 
 
 Documentation Sources
 ---------------------
 

-The formal ONAP 'NewDelhi' Release Documentation is available
+The formal ONAP Release Documentation is available

 in :ref:`ReadTheDocs<master_index>`.
 
 The `Developer Wiki <http://wiki.onap.org>`_ remains a good source of
 in :ref:`ReadTheDocs<master_index>`.
 
 The `Developer Wiki <http://wiki.onap.org>`_ remains a good source of


@@ -120,25 +93,11 @@ ONAP has adopted the `OpenSSF Best Practice Badge Program <https://bestpractices
 - `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
 
 
 - `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
 
 

-In the NewDelhi release,
-
-- 100% projects passed 95% of the OpenSSF badge
-- 94% passed the OpenSSF badge
-- 24% projects passed the OpenSSF Silver badge
-- 1 project passed the OpenSSF Gold badge
-

 Project specific details are in the :ref:`release notes<component-release-notes>`
 for each component.
 
 .. index:: maturity
 
 Project specific details are in the :ref:`release notes<component-release-notes>`
 for each component.
 
 .. index:: maturity
 

-ONAP Maturity Testing Notes
----------------------------
-For the 'NewDelhi' 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
 ----------------------------
 Known Issues and limitations are documented in each
 Known Issues and Limitations
 ----------------------------
 Known Issues and limitations are documented in each