...
Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).SDC will contribute to support:
Use Case: Residential Broadband vCPE (Approved)
SDC will continue to support:
Minimum Viable Product
Describe the MVP for this release.
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|
| Deliverable Location | ||
|---|---|---|
| SDC Docker Images | Exacutable | Docker image available at nexus3 |
| Java Source Code | The Java code for the main SDC components. | sdc Git repository's |
| Deployment Scripts | Chef recipes used to configure the Docker containers. | sdc Git repository's |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the API this release is expecting from other 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.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out 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 the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.