FOR REVIEW: Updated table of Meta-release Milestones

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 Send kick-off message to all@lists.camaraproject.org Close to M1, check final alpha release PR of Commonalities & ICM and submit to TSC for approval Announce M1 milestone and inform API Sub-projects Commonalities & ICM Define the scope 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 Create final alpha release PR and submit to Release Management After TSC approval: create approved alpha release of Commonalities & ICM TSC Approve alpha release 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 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 Release Management Check public-release PR of Commonalities and ICM If OK, submit to TSC for approval Announce M2 milestone and inform API Sub-projects TSC Approve public-release PR 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 Create API release tracking page for the API if it does not yet exist Create API release tracker for the API version Define scope of API release: Record scope in dedicated GitHub issue. Submit scope for TSC review Develop API scope through one or more alpha release(s) Update the API release tracker with each alpha release Create final alpha release and submit to Release Management After TSC approval: Create API alpha release Update the API release tracker with alpha release information Release Management Check API alpha release and, if OK, submit to TSC for approval Announce M3 milestone when all API alpha releases are reviewed by TSC TSC Review proposed alpha API releases	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 public-release PR to Release Management for checking After TSC approval: Create API public-release Update the API release tracker with public-release information 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 API Sub-project APIs	10 weeks
M4	Public-release APIs	M3 + 10 weeks	20
starts @ public-release PR for an API	Release Management Notify all teams to create their public-release on wg-release-management@lists.camaraproject.org 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 Send M5 meta-release announcement to all@lists.camaraproject.org TSC: Meta-release approval Commonalities & ICM Update public-release information on meta-release plan API Sub-projects Update API release tracker to reflect public-release API version	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