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 »


Assumptions:

  • Release, Security and Documentation scopes are now tracked via JIRA
  • Adoption to “Do not break the build” principle
  • No Vendor equipment is required for this release
  • No new VNF requirement identified by the project team
  • Jenkins Jobs Failures are monitored and fixed by the project team
  • Health check and regression tests issues are reported by the Integration Team
  • Project Team defines their Sprint content based on TSC prioritization to meet the delivery deadlines
  • Inform TSC about any descope content post-M1 before changing FixVersion

JIRA Template

Note that these Epics and Tasks are cloned into the JIRA project for each individual ONAP project.

CIMAN-323 - Getting issue details... STATUS

M1 

  • Any Architecture changes (Y/N)? Yes then require a ArchComm review plan
  • Any API changes Y/N
  • Any Data Model change Y/N
  • Any Impact on other components (Y/N)
  • Frankfurt Release Platform Maturity v1 == Dublin goals - update M1 Target
  • New 3rd party dependencies, new FOSS? Y/N
  • CII badging update
  • Change build process to adopt new oparent
  • Project specific test plan (automated unit test, sanity test/CSIT, pair-wise testing, etc) for Early Drop and full scope
  • 55% code coverage (set final goal after accessing jScript impacts) 
  • Fix Waiver granted by TSC from previous release
  • Fill in the  Release Planning Template

M2/M3

  • API docs complete
  • Data Models (e.g, JSON, YANG, Swagger, etc.) shared with Modeling/Community
  • Architecture Review complete (if required)
  • No Gerrit requests older than 36 hrs.
  • Provide docker to integration testing for Wave1
  • OOM port list update
  • Fix any Integration blocker - Daily status updates on integration blockers, Highest/High issues
  • Review and plan resolution of any License scan, security issues
  • Begin release notes for Early Drop
  • Update Frankfurt Risks

M4

  • License scan issues addressed
  • Address all security issues
  • All high/highest priority jira tickets addressed
  • Update Frankfurt Release Platform Maturity v1, CII badging update - update M4 Result
  • Test coverage goals complete
  • No Gerrit requests older than 36 hrs.
  • Integration weather board update
  • Update Frankfurt Risks

RCx

  • All high/highest priority jira tickets addressed
  • Remaining License scan, security critical issues addressed
  • Update Release note and documentation
  • Docker images “Release” dues 
  • Project specific test plan for El Alto completed
  • Update Frankfurt Risks
  • Integration Weather Board complete
  • Versioning at the project level
  • Check the certification expiry of your application. It should be valid for the next 9 months after RC0.

Sign-off

  • Remaining high/highest priority jira tickets addressed or workaround documented
  • Close/move all open/in-process jiras to a future release
  • Integration "Sign-Off" on Docker images “Release” 
  • Release notes and documentation completed
  • OOM tag release and version in helm chart
  • Update the Frankfurt Release Key Updates
  • No labels