The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
Requirement Epic | TSC Priority | SDC Epic(s) and/or SDC Story(ies) | Committed Contributors | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RANK #3 – PTL GO / NO GO |
| Ercisson, Orange OK | |||||||||||||||||||||||
| RANK #2 – Continuity |
| Ericsson | ?Waiting Component commitsupport on SDC see Req Jira for details | ||||||||||||||||||||||
| RANK | #4#3 – | CurrentlyPTL GO / NO GO | – Need Info (no later than June 30th, 2020)
| China Mobile OK See discussion in REQ Jira | |||||||||||||||||||||
| RANK #0 – TSC Special GO |
| SDC (S): Lumina, Huawei | OKWaiting assignment on SDC storyOrange stories created and assigned | ||||||||||||||||||||||
| RANK #0 – TSC Special GO |
| Ericsson, Nokia OK Ericsson contributing to 349 NF |
18 Non functionals :
10 - TSC MUST HAVE (please indicate where you plan to contribute)
Requirement Epic | TSC Priority | SDC Epic(s) and/or SDC Story(ies) | Committed Contributors | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
REQ-323 - Each project will update the vulnerable direct dependencies in their code base To Do | RANK #1 - Must Have |
|
Mentee SDC (Amir) supported by AT&T mentor | ||||||||||||
RANK #1 - Must Have |
|
| |||||||||||||
RANK #1 - Must Have |
|
| |||||||||||||
RANK #1 - Must Have |
|
| |||||||||||||
RANK #1 - Must Have |
|
| |||||||||||||
RANK #1 - Must Have |
|
| |||||||||||||
RANK #1 - Must Have |
|
| |||||||||||||
RANK #1 - Must Have |
|
| |||||||||||||
REQ-349 - Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage To Do | RANK #1 - Must Have |
|
| ||||||||||||
RANK #1 - Must Have |
|
|
...
RANK #2 – Continuity |
|
|
7- TSC PRIORITY 3 PTL GO/NO GO (please indicate where you plan to contribute)
|
| ?
Agreed as a Stretch goal | ||||||||||||||
|
| |||||||||||||||
|
| |||||||||||||||
|
| |||||||||||||||
REQ-360 - Application config should be fully prepared before starting the application container To Do |
|
| ||||||||||||||
REQ-350 - Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. To Do |
|
| ||||||||||||||
|
|
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the API this project is expecting from other projects.
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.
...
Name | Description | Version |
---|---|---|
Cassandra | Open-source distributed storage system | 3.1 |
Docker | VM container | |
JanusGraph | Open-source, distributed graph database | 1.0.0 |
Jetty | Open-source application server |
|
Ubuntu | Open-source software operating system | 16.0.4-LTS |
vnc | vnc server used for ui testing |
|
...
Please update any risk on the centralized wiki page - Frankfurt Risks – To be updated when avail
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...