...
| Scope | Priority | Committer Lead | Resources Committed | Epic | Dependencies | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CLAMP Self Serve Control Loop | high | AT&T, Ericscson |
| DCAE | |||||||||||
| CLAMP use policy model for Ops Policy | high | AT&T, Ericcsson |
| Policy | |||||||||||
| CLAMP - CDS integration | high | vidyashree.rama | AT&T, Huawei |
| CDS | ||||||||||
| SearchGuard to OpenDistro move | high | AT&T |
| ||||||||||||
| Document current upgrade component strategy | high | AT&T |
| ||||||||||||
| SECCOM Password removal from OOM HELM charts | high | AT&T |
| ||||||||||||
| SECCOM Perform Software Composition Analysis - Vulnerability tables | high | AT&T |
...
Please check the centralized wiki page: Frankfurt Release Platform Maturity v1
API Incoming Dependencies
List the API this release is expecting from other ONAP component(s) releases.
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.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
Known Defects and Issues
Please refer to Frankfurt Defect Status
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
Please update any risk on the centralized wiki page - Frankfurt Risks
Resources
Link toward the Resources Committed to the Release centralized page.
Release Milestone
...
Each project must edit its project table available at Project FOSS
Charter Compliance
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.