Page Comparison

...

Milestone	Milestone Name	Actions to achieve milestone	Timeline	Week number
Kickoff - M0	Start of release cycle.		M0	0
M1	Initiate Commonalities & ICM	Scope of Work Products clarified and recorded in dedicated issue. Identify commonalities work products. Create alpha release for Commonalities & ICM Create initial PRs for commonalities. Agree on the scope of commonalities. TSC review.	M0 + 2 week	2
M2	Finalize Commonalities & ICM	Create release-candidate for Commonalities & ICM Prepare public-release for Commonalities & ICM. Complete initial PR reviews. TSC Approval.	M1 + 10 weeks	12
M3	Initiate Sub-projects / APIs	Scope Request to 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 Define API test cases. Define acceptance criteria. Create alpha release for for Sub-projects / APIs.	M1 + 8 weeks	10
M4	Finalize Sub-projects / APIs	Conduct testing and log test result. Evaluate and log acceptance criteria. Code Freeze Create release-candidate for Sub-Projects / APIs. Prepare public-release for Sub-Projects / APIs. Request approval of Sub-projects / APIs to Release Management WG for meta-release	M3 + 10 weeks	20
M5	Meta Release	Determine the acceptance of the release-candidates for inclusion in the meta-release Bundle & publish meta-release TSC Approval Publish meta-release	M4 + 2 weeks	22
M6	Post- Release	Review release process and identify areas for improvement. Release Retro. Inputs from Sub Projects TSC Approval.	M5 + 2 weeks	24

Milestone	Milestone Name	Actions to achieve next milestone	Timeline	Week number
Kickoff - M0	Start of release cycle.		M0	0
		Scope of Work Products clarified and recorded in dedicated issue. Identify commonalities work products. Create alpha release for Commonalities & ICM Create initial PRs for commonalities. Agree on the scope of commonalities. TSC review.	2 weeks
M1	Initiate Commonalities & ICM		M0 + 2 weeks	2
		Create release-candidate for Commonalities & ICM Prepare public-release for Commonalities & ICM. Complete initial PR reviews. TSC Approval.	10 weeks
M2	Finalize Commonalities & ICM		M1 + 10 weeks	12
		Scope Request to 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 Define API test cases. Define acceptance criteria. Create alpha release for for Sub-projects / APIs.	8 weeks
M3	Initiate Sub-projects / APIs		M1 + 8 weeks	10
		Conduct testing and log test result. Evaluate and log acceptance criteria. Code Freeze Create release-candidate for Sub-Projects / APIs. Prepare public-release for Sub-Projects / APIs. Request approval of Sub-projects / APIs to Release Management WG for meta-release	10 weeks
M4	Finalize Sub-projects / APIs		M3 + 10 weeks	20
		Determine the acceptance of the release-candidates for inclusion in the meta-release Bundle & publish meta-release TSC Approval Publish meta-release	2 weeks
M5	Meta Release		M4 + 2 weeks	22
		Review release process and identify areas for improvement. Release Retro. Inputs from Sub Projects TSC Approval.	2 weeks
M6	Post- Release		M5 + 2 weeks	24

Milestone	Milestone Name	Actions to achieve next milestone Commonalities & ICM	Actions to achieve next milestone API Sub-projects	Timeline	Week number
Kickoff - M0	Start of meta-release			M0	0
		Scope of Work Products clarified and recorded in dedicated issue. Identify commonalities work products. Create alpha release for Commonalities & ICM Create initial PRs for commonalities. Agree on the scope of commonalities. TSC review.		2 weeks
M1	Initial Commonalities & ICM			M0 + 2 weeks	2
		Create release-candidate for Commonalities & ICM Prepare public-release for Commonalities & ICM. Complete initial PR reviews. TSC Approval.		10 weeks
M2	Final Commonalities & ICM			M1 + 10 weeks	12
			Scope Request to 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 Define API test cases. Define acceptance criteria. Create alpha release for for Sub-projects / APIs.	8 weeks
M3	Initial Sub-projects / APIs			M1 + 8 weeks	10
			Conduct testing and log test result. Evaluate and log acceptance criteria. Code Freeze Create release-candidate for Sub-Projects / APIs. Prepare public-release for Sub-Projects / APIs. Request approval of Sub-projects / APIs to Release Management WG for meta-release	10 weeks
M4	Final Sub-projects / APIs			M3 + 10 weeks	20
			Determine the acceptance of the release-candidates for inclusion in the meta-release Bundle & publish meta-release TSC Approval Publish meta-release	2 weeks
M5	Meta Release			M4 + 2 weeks	22
		Review release process and identify areas for improvement. Release Retro. Inputs from Sub Projects TSC Approval.		2 weeks
M6	Post Release			M5 + 2 weeks	24

Entity	M0	M1 (M0+2 weeks)
All	Kickoff
Commonalities & ICM		Scope of Work Products clarified and recorded in dedicated issue. Identify commonalities work products. Create alpha release for Commonalities & ICM Create initial PRs for commonalities. Agree on the scope of commonalities. TSC review.

Release cadence

CAMARA meta-releases are scheduled twice per year at approximately 6 month intervals (March and September). Meta-releases are named after major world cities in alphabetical order.

...

Versions Compared

Old Version 1

New Version 2

Key

Release cadence