...
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Requirements Epics for Guilin, impacting
...
SO
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = SO AND issuetype = Epic AND fixVersion = "Guilin Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Requirement | SO | SO Epic(s) / Story(ies) | M1 Scope and clarification | ||||||||||||||||||||||||||||
| REQ-339 - Container Network Function Test Platform (CNTP): OVP 2.0 support and Enable Network Service testing TO DO | x |
| Huawei Requirement is presented in the CNF task force and is accepted Stories to be updated for the requirement. Non functional requirement Identified: | ||||||||||||||||||||||||||||
REQ-324 - Support xNF Software Upgrade in association to schema updates IN PROGRESS | x |
| Ericsson, Orange This is already reviewed in the SO weekly and is accepted. commitment on the Non functional requirement is required. | ||||||||||||||||||||||||||||
| x |
| Nokia
Scope and Resource commitment and the non functional requirement need clarifications. | |||||||||||||||||||||||||||||
| x |
| Lumina, Huawei, Att The requirement is presented in the CNF task force meeting and is accepted. Non Functional requirement, | |||||||||||||||||||||||||||||
| x |
| Huawei, (Nokia - initial support in the design) The requirement is presented in the SO weekly meeting and is accepted. Non-Functional Requirement. | |||||||||||||||||||||||||||||
| x |
| Ericsson, Verizon The requirement is presented in the ETSI taskforce meeting and is accepted. Non-Functional Requirement:
|
...
Please fill out the centralized wiki page: Guilin Release Platform Maturity
Team Internal Milestone (Tentative)
API Incoming Dependencies
| Milestone | Description | Date | Comments |
|---|---|---|---|
| M2/M3 | Functionality Freeze / API Freeze | ||
| July 3, 2020 | Last day to submit Guilin swagger / Yang changes to Gerrit | |
| Aug 3, 2020 | Release manager reviews worksheets to assess readiness for M2/M3 milestone | |
| Aug 6, 2020 | ||
| M4 | Code Freeze | ||
| Sept 4, 2020 | Last day to submit Frankfurt code changes to Gerrit | |
| Sept 7, 2020 | Release manager reviews worksheets to assess readiness for M4 milestone, including the following checks:
| |
| Sept 7, 2020 | ||
| Sept 10, 2020 | ||
| RC0 | Release Candidate 0 | ||
| Sept 25, 2020 | Last date to submit code fixes for release candidate 0 | |
| Sept 28, 2020 | ||
| Sept 28, 2020 | ||
| Oct 1, 2020 | ||
| RC1 | Release Candidate 1 | ||
| Oct 9, 2020 | Last date to submit code fixes for Frankfurt release candidate 1 | |
| Oct 12, 2020 | ||
| Oct 12, 2020 | ||
| Oct 15, 2020 | ||
| RC2 | Release Candidate 2 | ||
| Oct 23, 2020 | Last date to submit code fixes for final Frankfurt release (RC2) | |
| Oct 26, 2020 | ||
| Oct 26, 2020 | ||
| Oct 29, 2020 | ||
| Release Sign-Off | Final TSC Sign-Off | May 7, 2020 | Frankfurt Release Sign-Off |
API Incoming Dependencies
List the API this project is expecting from other projectsList 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.
...
Base docker images with approved set of License to be used to construct SDC base SO base images.
Testing and Integration Plans
...
- validate uses cases and pairwise testing of SDC with SO with other components
- enhance CSIT to include more tests
...