| Kickoff - M0 | Start of release cycle. |
| M0 |
| M0 | 0 |
| M1 | Initiate Commonalities & ICM | - Scope of Work Products clarifiedclarified and recorded in dedicated issue.
- Identify commonalities work products.
- Create alpha release for Commonalities and ICM
- Create initial PRs for commonalities.
- Agree on the scope of commonalities.
- TSC Approvalreview.
| M0 + 2 week |
| M0 + 2 week | 2 |
| M2 | Finalize Commonalities & ICM | - Create release-candidate for Commonalities and ICM
- Prepare public-release for Commonalities & ICMRelease of Commonalities.
- Complete initial PR reviews.
- TSC Approval.
| M1 + 7 weeks |
| M1 + 8 (+2) weeks | 12 |
| M3 | Initiate Sub-Projects / APIs | - Scope Request to Sub-Projects / APIs.
- Determine requirements for subSub-projects / APIs.
- Create PRs for subSub-projects / APIs.
- Review and finalize PRs.
- Confirm scope of subSub-projects / APIs
- Define API test cases.
- Define acceptance criteria.
- Identify Create alpha release candidates for for subSub-projects / APIs.
| M1 + 6 weeks |
| M1 + 6 (+2) weeks | 10 |
| M4 | Finalize Sub-projects / APIs | - Conduct testing and log test result.
- Evaluate and log acceptance criteria.
- Code Freeze
- Create release candidate of release-candidate for Sub-Projects / APIs.
- Prepare public-release for Sub-Projects / APIs.
- Submit RC to release management WG for Meta ReleaseRequest approval of Sub-projects / APIs to Release Management WG for meta-release
| M3 + 8 (+2) weeks |
| M3 + 8 (+2) weeks | 20 |
| M5 | Meta Release | - Determine the acceptance of the RC for Meta Releaserelease-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish Meta Releasemeta-release
| M4 + 2 weeks |
| M4 + 2 weeks | 22 |
| M6 | Post- Release | - Review release process and identify areas for improvement.
- Release Retro.
- TSC Approval.
| M5 + 2 weeks |
| M5 + 2 weeks | 24 |