...
Release milestones and their associated tasks, are used to track the status of the release. The milestones and management tasks used in the release process are described in the table below.
| Milestone | Description | Timeline |
|---|---|---|
| Kickoff - M0 | Start of release cycle. | M0 |
| Initiate Commonalities & ICM - M1 | Scope of Work Products clarified. | M0 + 1 week |
| - Identify commonalities work products. | ||
| - Gather requirements for commonalities. | ||
| - Create initial PRs for commonalities. | ||
| - Complete initial PR reviews. | ||
| - Agree on the scope of commonalities. | ||
| - Select release candidates for commonalities. | ||
| TSC Approval. | ||
| Finalize Commonalities & ICM - M2 | Release of Commonalities. | M1 + 4 weeks |
| TSC Approval. | ||
| Initiate Sub-Projects / APIs - M3 | Scope Request to Sub-Projects / APIs. | M1 + 6 weeks |
| - Determine requirements for sub-projects/APIs. | ||
| - Create PRs for sub-projects/APIs. | ||
| - Review and finalize PRs. | ||
| - Confirm scope of sub-projects/APIs. | ||
| - Identify release candidates for sub-projects/APIs. | ||
| Finalize Sub-projects / APIs - M4 | Release of Sub-Projects / APIs. | M3 + 2 weeks |
| Testing & Acceptance. |
| - Conduct testing. | ||
| - Evaluate acceptance criteria. | ||
| Code Freeze | ||
| Meta Release | Release Retro. | M4 + 8 weeks |
| - Review release process and identify areas for improvement. | ||
| TSC Approval. | ||
Bundle & publish release - Common Release Date ("packaging done for the community release"). |
....................................
...