...
The purpose of this document is to describe the cadence, processes, milestones, and associated tasks used in the CAMARA release cycle. See CAMARA Releasesmeta-releases for information and schedule for specific releases.
...
| Milestone | Milestone Name | Description | Timeline |
|---|
| Kickoff - M0 | Start of release cycle. |
| M0 |
| 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 |
| M2 | Finalize Commonalities & ICM | - Release of Commonalities.
- Complete initial PR reviews.
- TSC Approval.
| M1 + 7 weeks |
| 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/APIs.
- Identify release candidates for sub-projects/APIs.
| M1 + 6 weeks |
| M4 | Finalize Sub-projects / APIs | - Release of Sub-Projects / APIs.
- Testing & Acceptance.
- Conduct testing.
- Evaluate acceptance criteria.
- Code Freeze
| M3 + 8 weeks |
| M5 | Meta Release | - Bundle & publish 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.
| M5 + 2 weeks |
Image Added
....................................
...