...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Guilin |
| Project Lifecycle State | Core |
| Participating Company | AT&T, Samsung, IBM |
Scope
What is this release trying to address?
Security enhancements and technology stack upgrade. More details tracked here - Requirements for Frankfurt - road map
Guilin Impact View per Component
Requirements
Specific new Usecases - N/A. Supports all existing ONAp ONAP usecase as per earlier releases.Requirements for Frankfurt - road map
Guilin Impact View per Component
Minimum Viable Product
Enhanced SecurityRich user experience through latest Angular upgrade and improved performance through Springboot upgrade.
Analytics Framework (aka Raptor) Upgrade to supports reports, charts etc
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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=PORTAL and issuetype in (story) and fixversion='Frankfurt Guilin Release' serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Indicate at a high level the longer term roadmaproad map. This is to put things into the big perspective.
Requirements for Frankfurt Guilin - road map
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this 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.
...
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Project Maturity Review for ONAP Portal
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 2 | 2 |
| |
| Stability | 2 | 2 |
| |
| Resiliency | 2 | 2 |
| |
| Security | 2 | 2 |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 2 | 2 |
| |
| Usability | 2 | 2 |
|
...
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.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
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).
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended recommended to provide these agreements and dates in this section.
...