...
- 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
- Fill in the Release Planning Template
- Assess Python3 migration status
- Assess Java 11 migration status
- Add project documents to document tracking table
...
- 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
- 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 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
...