...
List all sub-components part of this release.
Activities related to sub-component must components must be in sync with the overall release.
Sub-components are and repositories are consolidate consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the other ONAP projects your depends on.
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Archiecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
---|---|---|---|---|
Performance |
| |||
Stability |
| |||
Resiliency |
| |||
Security |
| |||
Scalability |
| |||
Manageability |
| |||
Usability |
|
API Incoming Dependencies
List the API this release project is expecting from other releasesprojects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
...
API Outgoing Dependencies
API this release project is delivering to other releasesprojects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
...