...
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 |
| M1 | 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- commonalities.- Select release candidates for - commonalities.
- TSC Approval.
| M0 + 1 week |
| M2 | Finalize Commonalities & ICM |
- M2 | - Release of Commonalities.
- Complete initial PR reviews.
- TSC Approval.
| M1 + 6 weeks |
TSC Approval.| M3 | Initiate Sub-Projects / APIs |
- M3 | - Scope Request to Sub-Projects / APIs.
|
M1 + 6 weeks | - - Determine requirements for sub-projects/APIs.
- Determine requirements for sub-projects/APIs.
|
- - Create PRs for sub-projects/APIs.
|
- - - Confirm scope of sub-projects/APIs.
|
- - Identify release candidates for sub-projects/APIs.
| M1 + 6 weeks |
| M4 | Finalize Sub-projects / APIs |
- M4 | - Release of Sub-Projects / APIs.
|
M3 + 8 weeks- - - Evaluate acceptance criteria.
- Code Freeze
| M3 + 8 weeks |
| M5 | Meta Release | |
Release Retro- Common Release Date ("packaging done for the community release").- Common Release Date ("packaging done for the community release").
| M4 + 2 weeks |
| M6 | Post- Release | - Review release process and identify areas for improvement.
- Release Retro.
- TSC Approval.
|
Bundle & publish release
....................................
...