The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | GuilinHonolulu |
| Project Lifecycle State | Core |
| Participating Company | Ericsson Software Technology, Deutsche Telekom, Orange, Nokia |
...
What is this release trying to address?
General project tasks:
- Support in
...
- producing composite documentation for ONAP releases
- Define guidelines and tooling for documentation handling across all ONAP projects
- Support project to understand requirements throughout the release cycle
Release specifics:
Improve templates
Refine the documentation guide
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
Minimum Viable Product
Describe the MVP for this release.
- Documentation process
- minimum scope for participating projects (planning, reviews, branching etc)
- Getting started with your documentation
- Suggestion to schedule a session for the upcoming virtual event
- Cleaning up outdated content
- Continuously clean up out dated content from RTD. How to do this in a structured way?
- Enable a voting job -1 for warnings (te be excluded long line)
- API Documentation handling
Functionalities
List the functionalities that this release is committing to deliver 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.
...
| Deliverable Name | Deliverable Description |
|---|---|
| Release documentation | Ensure that the project delivers documentation according to expectations |
...
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
...
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.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
API Outgoing Dependencies
API this project is delivering to other projects.
...
Resources
Fill out the Resources Committed to the Release centralized page.
...