| Kickoff - M0 | Start of release cycle. |
| M0 |
| M0 | 0 |
| M1 | Initiate Commonalities & ICM | - Scope of Work Products clarified.
- Identify commonalities work products.
- Create initial PRs for commonalities.
- Agree on the scope of commonalities.
- TSC Approval.
| M0 + 2 week |
| M0 + 2 week | 2 |
| M2 | Finalize Commonalities & ICM | - Release 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 sub-projects/APIs.
- Determine requirements for sub-projects/APIs.
- Create PRs for sub-projects/APIs.
- Review and finalize PRs.
- Confirm scope of sub-projects/APIsAPIs
- Define API test cases.
- Define acceptance criteria.
- Identify release candidates for sub-projects/APIs.
| M1 + 6 weeks |
| M1 + 6 (+2) weeks | 10 |
| M4 | Finalize Sub-projects / APIsRelease of Sub-Projects / APIs.Testing & Acceptance. | - Conduct testing.
- Evaluate acceptance criteria.
- Code Freeze
- Create release candidate of Sub-Projects / APIs.
- Submit RC 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 Release
- Bundle & publish release
- Common Release Date ("packaging done for the community 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 |