Jakarta Release Requirements
- David McBride
- cl664y@att.com
The page is intended to summarize all the requirements for Jakarta Release.
Candidate requirement proposals will be frozen on TBD
The Release Scope should be finalized during the M1 Release Planning milestone.
Note: we will no longer be using a Confluence table to track requirements. More information here.
New Cadence Terminology
Use case: High level feature that ONAP is supposed to support. Require Arch review, Req review, Impacted PTL review, all has to be GO from all the PTLs.
Feature: Functional change that touches multiple components (formely Functional REQuirement). Require Arch review, Req review, Impacted PTL review, all has to be GO from all the PTLs.
Spec: Functional change that is touching only a single project (formely Functional REQuirement). Require PTL to decide GO/NO GO, single component impact.
Best Practice: Design pattern recognized by the community. Must be followed by the new code associated to new container(s). The best practice owners to present their best practice to the PTLs and then to the TSC to review/to approve as best practice.
Global requirement: Best Practice that must be applied to whole code base during a particular release (formely called TSC MUST HAVE). The best practice owners to present their approved best practices to the PTLs and then to the TSC to review/to approve as GR at M1.
POC - POC definition - Developer Wiki - Confluence (onap.org)