• 1 Overview
• 2 Scope
  • 2.1 What is this release trying to address?
  • 2.2 Use Cases
  • 2.3 Requirements
  • 2.4 Minimum Viable Product
  • 2.5 Functionalities
    • 2.5.1 Epics
    • 2.5.2 Stories
  • 2.6 Longer term roadmap
• 3 Release Deliverables
• 4 Sub-Components
• 5 Architecture
  • 5.1 High level architecture diagram
  • 5.2 Platform Maturity
  • 5.3 API Incoming Dependencies
  • 5.4 API Outgoing Dependencies
  • 5.5 Third Party Products Dependencies
• 6 Testing and Integration Plans
• 7 Gaps
• 8 Known Defects and Issues
• 9 Risks
• 10 Resources
• 11 Release Milestone
• 12 Team Internal Milestone
• 13 Documentation, Training
• 14 Other Information
  • 14.1 Vendor Neutral
  • 14.2 Free and Open Source Software

Overview

...

E2E Network Slicing Use Case in R7 Guilin

POC:   Intent-Based NetworkNetwork#ScopeforGrelease

Requirements

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

...

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

POC:

Stories

...

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.

...

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.