...
The content of this template is expected to be fill out for M1 Release Planning Milestone - due 27 June via Release Planning
20180627_ still filling out - Michael O'Brien
| Table of Contents | ||
|---|---|---|
|
Overview
| Logging | Logging |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | Amdocs, AT&T, Bell |
...
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.
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
|---|---|---|---|---|---|
| To fill out | High level description of the APIPOMBA Audit Inititiation | API to inititiate POMBA Audit | Date for which the API is reviewed and agreed | To fill outLink toward the detailed API description | |
| POMBA Context Builders | API that must be supported by all Context Builders | POMBA Context Builder Swagger |
Third Party Products Dependencies
...
| 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
...