The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
The following table lists the new functional requirements SDNC is committing to support for the Honolulu Istanbul Release:
| Requirements | Companies Supporting Requirement | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| IBM | ||||||||||
| IBM, Wipro | ||||||||||
| Huawei | ||||||||||
| Ericsson |
Minimum Viable Product
The following epics represent the minimum viable product of the SDNC Istanbul Release:
...
The following epics are also in scope for HonoluluIstanbul, but are not considered of the minimum viable product. In the event of unanticipated resource constraints, these could be reduced in scope or deferred without impacting any functionality deemed by the TSC as critical for HonoluluIstanbul.
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project="Network Controller" and issuetype in (epic) and (labels != relman OR labels is EMPTY) and fixversion="Istanbul Release" and priority < high serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
| Deliverable Name | Deliverable Description | Deliverable Location |
|---|---|---|
| SDNC Source Code | Source code for SDNC project | ONAP gerrit |
| SDNC Maven Artifacts | Compiled code that can be referenced in other projects as maven dependencies | ONAP Nexus |
| SDNC Docker Containers | Docker containers associated with SDNC project:
| ONAP Nexus |
| Documentation | User and developer guides | ONAP Wiki |
| SDNC CI/CD automation | Scripts to automate compilation and deployment of maven artifacts and docker containers | ONAP gerrit ONAP Jenkins |
Sub-Components
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:sdnc
...
Please fill out the centralized wiki page: Honolulu Istanbul Release Platform Maturity
API Incoming Dependencies
...
Please update any risk on the centralized wiki page - Honolulu Risks Istanbul Risks
Resources
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:sdnc
...
The milestones are defined at the Release Planning: Honolulu Istanbul and all the supporting project agreed to comply with these dates.
Team Internal Milestone
| Anchor | ||||
|---|---|---|---|---|
|
| Milestone | Description | Date | Comments |
|---|---|---|---|
| M2 | Spec Freeze |
| |
| M3 | Final Code Submission |
| Last date for code reviews to be submitted for Istanbul user stories |
| M4 | Feature Freeze | ||
|
|
| |
|
| ||
|
| Released dockers must be built and code reviews submitted to OOM to bump to Istanbul M4 versions | |
| RC | Release Candidate | ||
|
| Last date to submit code fixes for |
| Istanbul RC0 | |||
|
| ||
| | ||
| Release Sign-Off | Final TSC Sign-Off | | Istanbul Release Sign-Off |
Documentation, Training
Please update the following centralized wiki: Istanbul Documentation
That includes
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- Team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...