Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
PerformanceNANAvvp is a stand alone tool not a platform component
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
StabilityNANAvvp is a stand alone tool not a platform component
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
ResiliencyNANAvvp is a stand alone tool not a platform component
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
SecurityNA0NA1vvp is a stand alone tool not a platform component
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
ScalabilityNANAvvp is a stand alone tool not a platform component
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
ManageabilityNANAvvp is a stand alone tool not a platform component
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
UsabilityNANAvvp is a stand alone tool not a platform component
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sanbox vvp and issuetype in (bug) and fixVersion=Beijing
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out
  • 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.

11/16/18M0Kickoff
1/18/18M1Planning process Complete
2/12/18M2Functionality Freeze
3/8/18M3API/Data Model Freeze
3/29/18

M4

Code Freeze

4/19/18

RC0

Release Candidate 0

5/23/18

RC1

Release Candidiate 1

5/17/18

RC2

Release Candidiate 2

5/24/18Release DeliveryTarget Release Date
  • Team Internal 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 to provide these agreements and dates in this section.

...