.. _onap-release-notes:
-'London' Release Notes
-======================
+'NewDelhi' Release Notes
+========================
-This page provides the release notes for the ONAP 'London' release. This
+This page provides the release notes for the ONAP 'NewDelhi' release. This
includes details of software versions, known limitations, and outstanding
trouble reports.
Details on the specific items delivered in each release by each component is
maintained in the component specific release notes.
-'London' Major Release 12.0.0
------------------------------
+'NewDelhi' Major Release 14.0.0
+-------------------------------
+-----------------------------------+-----------------------------------------+
| **Project** | Open Network Automation Platform (ONAP) |
+-----------------------------------+-----------------------------------------+
-| **Release name** | London |
+| **Release name** | NewDelhi |
+-----------------------------------+-----------------------------------------+
-| **Release version** | 12.0.0 |
+| **Release version** | 14.0.0 |
+-----------------------------------+-----------------------------------------+
-| **Release date** | 2023, not released yet |
+| **Release date** | 2024, not released yet |
+-----------------------------------+-----------------------------------------+
-Features
---------
-
-ONAP 'London' focusses on:
-
-- to be done
-
-Functional Requirements
------------------------
-
-Richer Set of Cloud Native Functionality
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-- to be done
-
-E2E Network Slicing
-^^^^^^^^^^^^^^^^^^^
-
-- to be done
-
-Control Loop Evolutions
-^^^^^^^^^^^^^^^^^^^^^^^
-
-- to be done
-
-Extended O-RAN Integration
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+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.
-- to be done
-
-Controllers
-^^^^^^^^^^^
-
-- to be done
-
-Service Design
-^^^^^^^^^^^^^^
-
-- to be done
-
-Inventory
-^^^^^^^^^
-
-- to be done
+OpenSSF Gold Standard
+---------------------
-ONAP Operations Manager
-^^^^^^^^^^^^^^^^^^^^^^^
+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.
-- to be done
+Java 17
+-------
-Non-Functional Requirements
----------------------------
+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.
-The following 'non-functional' requirements are followed in the
-'London' Release:
+CPS
+---
-Best Practice
-^^^^^^^^^^^^^
+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.
-- to be done
+Modeling
+--------
-Security
-^^^^^^^^
+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.
-- to be done
+OOM
+---
-Documentation
-^^^^^^^^^^^^^
+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.
-- to be done
+SDC
+---
-Tests & Integration
-^^^^^^^^^^^^^^^^^^^
+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.
-- to be done
+CCSDK
+-----
-<additional section to be added?>
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+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.
-- to be done
+PortalNG
+--------s
-.. important::
- Some non-functional requirements are not fully finalized. Please, check details
- on the :doc:`Integration <onap-integration:usecases/release_non_functional_requirements>`
+We introduced new PortalNG 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
---------------------
-The formal ONAP 'London' Release Documentation is available
+The formal ONAP 'NewDelhi' Release Documentation is available
in :ref:`ReadTheDocs<master_index>`.
The `Developer Wiki <http://wiki.onap.org>`_ remains a good source of
- `Badging Requirements <https://github.com/coreinfrastructure/best-practices-badge>`_
- `Badging Status for all ONAP projects <https://bestpractices.coreinfrastructure.org/en/projects?q=onap>`_
-In the London release,
-- 100% projects passed 90% of the OpenSSF badge
-- 86% passed the OpenSSF badge
-- 11% projects passed the OpenSSF Silver badge
+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.
ONAP Maturity Testing Notes
---------------------------
-For the 'London' release, ONAP continues to improve in multiple areas of
+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>`
Code Review / doc.git / blobdiff