Page Comparison

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

Meta-release kickoff

Release Management (before M0)

• Send kick-off message to release@lists all@lists.camaraproject.org
• Notify Outreach CommitteeCheck final alpha release PR and submit to TSC for approval
• Announce M1 milestone and inform API Sub-projects

Commonalities & ICM

• Finalize release Define the 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 Create final alpha releases PRs for TSC review:If OK: create final alpha release for release PR and submit to Release Management
• After TSC approval: create approved alpha release of Commonalities & ICM
• Send Commonalitie & ICM alpha release message to release@lists.camaraproject.org

TSC

• Review final Approve alpha releases release PRs of Commonalities & ICM

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 approvedCreate public-release PR and submit to Release Management
• After TSC approval:
  • Create
  final release-candidates
  • the public-release PR for Commonalities & ICM
  • Update the meta-release page for Commonalities & ICM

Release Management

• Prepare Check public-release PR for of Commonalities & ICM for M5

TSC

• Approval of final release-candidates PRs 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

M2

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
• 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 Create final alpha API release PR for TSC review:If OK: create final alpha releases for the APIrelease 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 final proposed alpha API release PRreleases

M3

M1 + 8 weeks

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 public-release -candidates PR to Release Management for checking
• After TSC approvalIf approved:
  • Create final API public-release
  • Update the API release -candidatePrepare tracker with public-release information

Release Management

• Check API public-release PR for M5and, if OK, submit to TSC for approval
• Announce M4 milestone when all API public-releases are approved by TSC

TSC

• • Approval of
final
• • API public-release
-candidate PR
• • PR for all API Sub-project APIs

M4

M3 + 10 weeks

starts @ M2 for Commonalities & ICMstarts @ public-release PR for an API

Release Management (this can start for each item, whenever the item public-release PR is made available)

• 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
• On After TSC approval,  
• notify approval on release@lists.camaraproject.org
• notify Outreach Committee
publish the meta-release information
• send Send M5 meta-release announcement to all CAMARA to all@lists.camaraproject.org 

TSC:

• Meta-release approval

Commonalities & ICM

• Publish new release through approved PR
• Update public-release information on meta-release plan

API Sub-projects

• Update API release tracker to reflect public-release API version & tag

M5

Release Management

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

TSC

• Meta-release improvements approval.

M6