Integration Release Planning
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Info
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Guilin |
Project Lifecycle State | Incubation |
Participating Company | See gerrit for the different Integration related repositoriries
Declarative wiki text is just declarative. Fortunately gerrit has all this information, dynamically updated and easily auditable. |
Scope
What is this release trying to address?
Same scope as usual
ensure integration
perform CI
support Intel/Windriver lab usage
support use cases
See Integration EPICs for new topics
Requirements
N.A
Minimum Viable Product
N.A
Functionalities
A dedicated Dashboard has been created for Guilin: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=221&selectedIssue=INT-1045
Epics
Stories
Longer term roadmap
More tests, More automation, More CI chains
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
|---|---|
To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the .
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Please fill out the centralized wiki page: Frankfurt Release Platform Maturity
API Incoming Dependencies
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.