...
The content of this template is expected to be fill out for M1 Release Planning reviewMilestone.
| Info | ||
|---|---|---|
| ||
Copy and Paste the content below into your wiki release root directory. |
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliver |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to Project Lifecycle for details on Project Lifecycle |
| Participating Company | List the company participating in this release. At least 3-4 organizations, including an operator are expectedrecommended. |
Scope
What is this release trying to address?
...
List the functionalities that this release is committing to deliver .
...
| title | Info |
|---|
List the functionalities proposed for this release.
Add one row for each functionality.
In Scope column, indicate if the functionality is IN (for sure it will be delivered) or OUT (the functionality has been discussed, and decision was to NOT deliver the functionality in this release).
...
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.
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key TEST-23
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Resources assigned to project are consolidated in a single place. Edit all the the table with the ALL information, that helps to expedite Linux Foundation operations.
| Role | First Name Last Name | Linux Foundation ID | Email Address | Location |
|---|---|---|---|---|
| Project Team Lead | Chengdu, China. UTC +8 | |||
| Primary Contact | may be same as team lead | |||
| Project Manager | if any | |||
| Committers | ||||
| committer name | ||||
| committer name | ||||
| Contributors | ||||
| contributor name | ||||
| contributor name |
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
Documentation, Training, Tutorial
- Highlight the team contributions to the overall Release Documentation and Training projects.
- 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
...