Updated table of CAMARA Release Process

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)

• Send kick-off message to release@lists.camaraproject.org

• Notify Outreach Committee

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

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:

• Meta-release approval

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

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

M0 - meta-release kickoff

M0

0

Release Management

• Prepare meta-release page

Commonalities & ICM

• Define scope of release.

  • Record scope in dedicated GitHub issue.

  • Submit scope for TSC review

• Develop Commonalities & ICM scope through one or more alpha release(s)

• Update release tracker on target meta-release page with each alpha release

• Submit final alpha releases PRs for TSC review:

• If OK: create final alpha releases for Commonalities & ICM

TSC

• Review final alpha releases PRs of Commonalities & ICM

2 weeks

M1 - Draft Commonalities & ICM

M0 + 2 weeks

2

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 - Final Commonalities & ICM

M1 + 10 weeks

12

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 - Draft APIs

M1 + 8 weeks

10

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 - Final APIs

M3 + 10 weeks

20

Release Management

• 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

• TSC meta-release approval

• Publish the meta-release

2 weeks

M5 - Meta Release

M4 + 2 weeks

22

Release Management

• Review release process and identify areas for improvement. 

• Release Retro.

  • Get inputs from Sub Projects

• TSC Approval.

2 weeks

M6 - Post Release

M5 + 2 weeks

24

Kickoff - M0