| 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 (before M0) Commonalities & ICM - Finalize release scope definition for meta-release.
- Record scope in dedicated GitHub issue.
- Submit scope issue for TSC review
- Develop Commonalities & ICM scope through one or more alpha release(s)
- Update data in the meta-release plan with each alpha release
- Submit final alpha releases PRs for TSC review:
- If OK: create final alpha release for Commonalities & ICM
- Send Commonalitie & ICM alpha release message to release@lists.camaraproject.org
TSC - Review final alpha releases PRs of Commonalities & ICM
| 2 weeks |
|
M1 | Alpha Commonalities & ICM | M0 + 2 weeks | 2 |
| starts @ M1 | Commonalities & ICM - Fix bugs raised by users through one or more release-candidates
- Update release tracker on target meta-release page with each release-candidate
- Submit final release-candidates PRs for TSC approval
- If approved:
- Create final release-candidates for Commonalities & ICM
- Prepare public-release PR for Commonalities & ICM for M5
TSC - Approval of final release-candidates PRs of Commonalities & ICM
| 10 weeks |
|
M2 | Release-candidate Commonalities & ICM | M1 + 10 weeks | 12 |
M1 | Alpha Commonalities & ICM | M0 + 2 weeks | 2 |
| starts @ M1 | API Sub-projects - Define scope of API release.
- Record scope in dedicated GitHub issue.
- Submit scope for TSC review
- Create API release tracker for the API version
- Develop API scope through one or more alpha release(s)
- Update the API release tracker with each alpha release
- Submit final alpha API release PR for TSC review:
- If OK: create final alpha releases for the API
TSC - Review final alpha API release PR
| 8 weeks |
|
M3 | Alpha APIs | 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 final API release-candidates PR for TSC approval
- If approved:
- Create final API release-candidate
- Prepare API public-release PR for M5
TSC - Approval of final API release-candidate PR
| 10 weeks |
|
M4 | Release-candidate APIs | M3 + 10 weeks | 20 |
starts @ M2 for Commonalities & ICM starts @ public-release PR for an API | Release Management (this can start for each item, whenever the item public-release PR is made available) - For Commonalities and ICM, check that all release assets are available in the public-release PR
- If OK: approve creation of public-release of Commonalities and ICM
- For each API release-candidate, check that all release assets are available in the API public-release PR
- Propose meta-release content to TSC
- On TSC approval,
- notify approval on release@lists.camaraproject.org
- notify Outreach Committee
- publish the meta-release information
- send meta-release announcement to all CAMARA
TSC: Commonalities & ICM - Publish new release through approved PR
- Update public-release information on meta-release plan
API Sub-projects - Publish new API release through approved PR
- Update API release tracker to reflect public-release API version & tag
| 2 weeks |
|
M5 | Meta-release | M4 + 2 weeks | 22 |
| starts @ M5 | Release Management - Review release process with teams and identify areas for improvement.
- Propose improvements for TSC approval
TSC - Meta-release improvements approval.
| 2 weeks |
|
M6 | Post Release | M5 + 2 weeks | 24 |