The content of this template is expected to be fill out for M1 Release Planning Milestone.

...

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.

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

Overview

...

•  Upgrade postgresql   USECASEUI-405 - 2 components in one Docker 处理中
•  Modify UUI certificates  Image ModifiedUSECASEUI-594 - UUI certificates are not correct
•  Modify returning coverageAreaTAList for AN slice profile   Image ModifiedUSECASEUI-618 - Fix issue in returning coverageAreaTAList for AN slice profile 

...

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 Architecture 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: Jakarta 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.

...

• Known Defects and Issues

Please refer to  Frankfurt Defect Statusthe "Bugs" section above

• Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Please update any risk on the centralized wiki page - Jakarta Risks

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

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

...

Please update the following centralized wiki: Jakarta Documentation

That includes

• Team contributions to the specific document related to he project (Config guide, installation guide...).
• Team contributions to the overall Release Documentation and training asset
• 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
  • ...

...

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

Charter Compliance

The project team comply with the ONAP Charter.