Page History

• Release Management

• Prepare : prepare meta-release page
• Request TSC to declare kickoff
• plan
• Commonalities & ICM

• : define scope and start alpha release development
• TSC: declare M0 -

• Starting from previous M2, prepare scope definition for meta-release.
• Implement scope in one or more alpha releases

TSC

• Declare meta-release kickoff

Meta-release kickoff

• Commonalities & ICM: fix scope and develop final alpha release for M1
• API Sub Groups: check Commonalities and ICM scope definition to assess API impact
• TSC: approve Commonalities and ICM scope and final alpha release
• Release Management: Declare M1 - Commonalities and ICM alpha release available

Release Management

• Announce M0 meta-release kick-off on all@lists.camaraproject.org
• Once available, check the final alpha releases of Commonalities & ICM and, if OK, submit to TSC for approval
• After TSC approval, announce M1 milestone

Commonalities & ICM

• Finalize the scope definition for meta-release.
  
  • Record scope in dedicated GitHub issue.
  • Submit scope issue for TSC review
• Develop final Commonalities & ICM scope through one or more alpha releases
• Update data in the meta-release plan with each alpha release
• Create final alpha release PRs and submit to Release Management
• After TSC approval, create approved final alpha release for Commonalities & ICM
• Update the meta-release plan with the alpha release tag

TSC

• Approve Commonalities and ICM scope
• Approve final alpha release PRs of Commonalities & ICM

M1

• API Sub Groups: align to Commonalities and ICM alpha release and provide feedback
• 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 : Fix bugs and prepare final release-candidate PR and submit to Release Managementfor M2
• TSC: approve Commonalities and ICM final After TSC approval:
• Create the final release-candidate for Commonalities & ICM
Update the meta-release page for Commonalities & ICM with release-candidate tag
• Release Management

• Check final release-candidate PRs of Commonalities and ICM and, if OK, submit to TSC for approval
• After TSC approval, and commit of ; declare M2 - Commonalities and ICM final release-candidate PRs, announce M2 milestone

TSC

• Approve final release-candidate PRs of Commonalities & ICM

• available

M2

• API Sub

• 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.
  • 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 PR and submit to Release Management
• After Release Management approval:
  • Create first release-candidate for the API
  • Update the API release tracker with the release-candidate tag

Release Management, for each API

• Once available, check the first API release-candidate PR and, if OK, approve PR
• Announce M3 milestone with all approved API release-candidates.

TSC

• Projects: prepare API scope and develop alpha releases, ending by the first release-candidate for M3
• TSC: review scope of APIs (case by case selection)
• Release Management: check API readiness of each API and declare M3 - all API first release-candidates availableReviewing scope of selected APIs (case by case selection)

M3

M1 + 9 weeks

• API Sub

• Projects: fix bugs and prepare public-release
• Commonalities & ICM: prepare public-release
• Release Management: check API readiness of each API and declare M4 - all API public-releases available
• TSC: give formal approval of Commonalities, ICM and API (case-by-case) public-releases

• Fix bugs raised by API testers through one or more release-candidates
• Update API release tracker with each release-candidate
• Submit final release-candidate PR to Release Management for checking
• After final release-candidate PR approval by Release Management:
  • Create final release-candidate and update API release tracker
  • Create API public-release PR
• After TSC approval of the PR
  • Create public-release
  • Update the API release tracker with public-release tag

Release Management

• Once available, check final API release-candidate PR and, if OK, approve PR
• Announce M4 milestone when all API public-releases are approved by TSC

Commonalities & ICM (through M3 upto M4)

• Fix bugs raised by API testers through one or more release-candidates
• Create public-release PR for Commonalities & ICM
• After TSC approval of the public-release PR
  • Create the public-release
  • Update the meta-release page with public-release tag

TSC

• Formal approval of the Commonalities & ICM public-release PRs
• Formal approval API public-release PRs

M4

M3 + 9 weeks

activities for M5 starts @ public-release PR for an API

• Release Management

• Check that all API release trackers are updated for the meta-release
• Propose : prepare and declare M5 - meta-release content to TSCavailability
• After TSC approval, publish the TSC: approve meta-release
• Announce the M5 meta-release on all@lists.camaraproject.org 

TSC:

• Meta-release approval

• for M5

M5

Release Management

• Review release process with all teams and identify areas for improvement. 
• Propose improvements for TSC approval

TSC

• Meta-release improvements approval.

• Commonalities & ICM: assess meta-release and provide feedback
• API Sub Groups: assess meta-release and provide feedback
• Release Management: assess meta-release, create improvement plan and declare M6 - post-release assessment available
• TSC: approve improvement plan for M6

M6