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.

• 1Overview
• 21 Overview
• 2 Scope
  • 2.11 What is this release trying to address?
  • 2.22 Use Cases
  • 2.33 Requirements
  • 2.44 Minimum Viable Product
  • 2.55 Functionalities
    • 2.5.11 Epics
    • 2.5.22 Stories
  • 2.66 Longer term roadmap
• 33 Release Deliverables
• 44 Sub-Components
• 55 Architecture
  • 5.11 High level architecture diagram
  • 5.22 Platform Maturity
  • 5.33 API Incoming Dependencies
  • 5.44 API Outgoing Dependencies
  • 5.55 Third Party Products Dependencies
• 66 Testing and Integration Plans
• 77 Gaps
• 88 Known Defects and Issues
• 99 Risks
• 1010 Resources
• 1111 Release Milestone
• 1212 Team Internal Milestone
• 1313 Documentation, Training
• 1414 Other Information
  • 14.11 Vendor Neutral
  • 14.22 Free and Open Source Software

Overview

...

JDK upgrade evaluate and migrate (Depend on the commit resource) and Upgrade PostgreSQL:

Upgrade Vulnerable Direct Dependencies: 

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

E2E Network Slicing Use Case in R7 Guilin

POC:  Intent-Based Network#ScopeforGrelease

Requirements

Describe the use case this release is targeted for (better if reference to customer requirements).

E2E Network Slicing: KPI Monitoring:

Transport Slicing for Guilin Release:  

Support for Intent-based Network:  

...

Usecase-UI will include the necessary subcomponents supporting the primary objectives: supporting the use cases and meeting platform maturity goals and supporting the use cases.

1. UUI BE Component  for supporting KPI Monitoring and Transporting Slicing
2. UUI FE Component  for supporting KPI Monitoring and Transporting Slicing

...

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.

Epics

Jira Legacy
server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery key = USECASEUI-446 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

keyREQ-342POC:

Stories

Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

Indicate where your project fit within the ONAP Archiecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

...

Please fill out the centralized wiki page: Frankfurt Guilin 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.

...

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.