You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 29
Next »
UPDATED PROPOSAL FOR REVIEW (2024-04-23)
Please review the table on this page - proposal is that it replaces the table on the Meta-release Milestones page.
Milestone / start date | Actors & Actions for next milestone | Timeline | Week Nr |
---|
pre-M0 | Release Management - Prepare meta-release page
- Request TSC to declare kickoff
Commonalities & ICM (from previous M2) - Prepare release scope definition for meta-release.
TSC - Declare meta-release kickoff
|
|
|
M0 | Meta-release kickoff | M0 | 0 |
starts @ M0 | Release Management - Check release-candidate PRs of Commonalities & ICM and, if OK, submit to TSC for approval
- After TSC approval, announce M1 milestone
Commonalities & ICM - Define the scope for meta-release.
- Record scope in dedicated GitHub issue.
- Submit scope issue for TSC review
- Update data in the meta-release plan with each alpha release
- and submit to Release Management
- After TSC approval: create approved first release-candidate of Commonalities & ICM
- Update the meta-release plan with the release tag
TSC | 2 weeks |
|
M1 | | M0 + 2 weeks | 2 |
starts @ M1 | Commonalities & ICM - Fix bugs raised by users through one or more release-candidates
- Update release tracker on meta-release page with each release-candidate
- Create public-release PR and submit to Release Management
- After TSC approval:
- Create the public-release PR for Commonalities & ICM
- Update the meta-release page for Commonalities & ICM with public-release tag
Release Management - Check public-release PRs of Commonalities and ICM and, if OK, submit to TSC for approval
- After TSC approval, announce M2 milestone
TSC - Approve public-release PR of Commonalities & ICM
| 10 weeks |
|
M2 | | M1 + 10 weeks | 12 |
| Release-candidate Commonalities & ICM | M0 + 2 weeks | 2 |
starts @ M1 | API Sub-projects - Create API release tracking page for the API if it does not yet exist
- Create API release tracker for the API version to be released
- Define scope of API release:
- Record scope in dedicated GitHub issue.
- Submit scope for TSC review
- Update the release tracker with the scope issue link
- Develop API scope through one or more alpha release(s)
- Update the API release tracker with each alpha release
- Create first release-candidate (x.y.z-rc.1) PR and submit to Release Management
- Update the API release tracker with the release-candidate tag
Release Management - Check API release-candidate PR and, if OK, submit to TSC for approval
- Announce M3 milestone when all API alpha releases are reviewed by TSC
TSC - Review proposed API release-candidate PR
| 8 weeks |
|
M3 | | M1 + 8 weeks | 10 |
starts @ M3 | API Sub-projects - Fix bugs raised by API testers through one or more release-candidates
- Update API release tracker with each release-candidate
- Submit public-release PR to Release Management for checking
- After TSC approval:
- Create API public-release (x.y.z)
- Update the API release tracker with public-release tag
Release Management - Check API public-release PR and, if OK, submit to TSC for approval
- Announce M4 milestone when all API public-releases are approved by TSC
TSC - Approval of API public-release PR for all proposed API Sub-project APIs
| 10 weeks |
|
M4 | | M3 + 10 weeks | 20 |
starts @ public-release PR for an API | Release Management - Check that all API release trackers are updated for the meta-release
- Propose meta-release content to TSC
- After TSC approval, publish the meta-release
- Announce the M5 meta-release on all@lists.camaraproject.org
TSC: | 2 weeks |
|
M5 | Meta-release | M4 + 2 weeks | 22 |
starts @ M5 | Release Management - Review release process with all teams and identify areas for improvement.
- Propose improvements for TSC approval
TSC - Meta-release improvements approval.
| 2 weeks |
|
M6 | Post Release Assessment | M5 + 2 weeks | 24 |