Page Comparison

...

• Define Frankfurt Scope with jira tickets labeled OR fixVersion
• Any Architecture changes (Y/N)? Yes then require a ArchComm review plan
• Any API changes Y/N
• Frankfurt Release Platform Maturity v1 == Dublin goals - update M1 Target
• New 3rd party dependencies, new FOSS? Y/N (Seed Code)
  
• CII badging update
• Review code coverage goal vs. actuals
• Change build process to adopt new oparent, Portal SDK - Anything else?
  
• Fill in the  Release Planning Template
• Assess Python3 migration status
• Assess Java 11 migration status
• Add project documents to document tracking table

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: oParent, PortalSDK
  
• 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 issuesBegin release notes for Early Drop
• Update Frankfurt Risks

M4

Note:  beginning with M4, we are customizing requirements for OOM, INT, VNFREQ, VNFSDK, and VVP.  M1 and M2/3 requirements will be customized beginning with Guilin. Customization is based on input from project PTLs.

Tasks/Deliverables	Most Projects	VVP	VNFREQ	INT
New 3rd party dependencies, new FOSS (final confirmation)
License scan issues addressed
Address all security issues
All high/highest priority jira tickets addressed
Update Frankfurt Release Platform Maturity

...

, CII badging update - update M4 Result
Test coverage goals complete
No Gerrit requests older than 36 hrs.
Integration weather board update
Update Frankfurt Risks

...

Lab resources secured for release validation
Use case readiness
CI/CD readiness
Integration test readiness
Tooling readiness

RC0

Tasks/Deliverables	Most Projects	VVP	VNFREQ	INT
All high/highest priority jira tickets (bugs) addressed
Remaining License scan, security critical issues addressed
Update Release note and documentation
Docker images “Release” dues
Project specific test plan

...

completed
Update Frankfurt Risks
Integration Weather Board complete
Versioning at the project level
Check the certification expiry of your application.

...

CI Daily for Release

RC1 (TBD)

• Update the Frankfurt Release Key Updates

Tasks/Deliverables	Most Projects	VVP	VNFREQ	INT
JIRA All stories, epics, tasks, and subtasks (except documentation) should be closed All high/highest priority tickets opened since RC0 should be closed
Docker image release including bug fixes
Integration test status updated with % complete and estimated days to completion (integration test status page)
CI Daily for Release

RC2 (TBD)

Tasks/Deliverables	Most Projects	VVP	VNFREQ	INT	Documentation
JIRA All stories, epics, tasks, and subtasks (except documentation) should be closed All high/highest priority tickets opened since RC1 should be closed
Finalize documentation Release notes, including security waivers
Final docker image
Integration Release test status shows 100% completed and zero days remaining for testing
CI Daily for Release
Publish release documentation Frankfurt branch for RTD Update main page to Frankfurt, including version number

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