Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The purpose of this document is to describe the milestones and associated tasks used in the ONAP release cycle.  See Project Status and Release Planning for information on specific releases.


MilestoneDescriptionProject TasksRequirement Owner Tasks
M0Start of release cycle

M1General requirements approved
  • Review Code Coverage goal vs. actuals
  • Update the FOSS wiki page
  • Request an architectural subcommittee review
  • Document API issues in the requirement description
  • Get approval and identify impact of Use Case, Feature, Spec, or Best Practice
  • Document API issues in the requirement description
M2

Specification freeze

  • Freeze the scope
  • Review approved Global Requirements
  • Verify that specifications and features are approved by affected projects
  • PTLs determine impact of features and specs on APIs
  • Complete release planning template
  • Add documents to document tracking table
  • Update documented risks
  • Review license scan issues
  • Complete Architectural subcommittee review
  • Data models shared with Modeling subcommittee
  • Verify that there are no merge requests older than 36 hours
  • Communicate API changes to other projects
  • Finalize documentation of API changes and share with affected PTLs
M3Feature freeze
  • Start OOM review with updated container image
  • Assign Jira issues to the release
  • Resolve all Global Requirement impacts
  • Complete preliminary documentation
  • Review and update INFO.yaml
  • Update integration weather board
  • Verify that test coverage goals have been met
  • Update Release Platform Maturity and CII badging
  • Resolve high/highest priority JIRA issues
  • Update the FOSS wiki page
  • Verify that there are no merge requests older than 36 hours
  • Review license scan issues
  • Document integration test tasks in Jira
  • Complete preliminary documentation
  • Review and update scope status
RC0Release Candidate 0 Integration and Test
  • Create a release branch
  • Complete marketing update
  • Update integration weather board and creat pairwise testing page
  • Resolve high/highest priority JIRA issues
  • Deliver updated container to integration team
  • Complete project testing
  • Review license scan issues
  • Update RC0 scorecard field
  • Update integration test tasks in Jira
  • Complete marketing update page
  • No labels