REVIEW CLOSED: Updated table of Meta-release Milestones

Owned by Tanja de Groot
Last updated: May 08, 2024
3 min read

TO BE ARCHIVED

Review closed (2024-04-30) - approved content move to Meta-release Milestones page. - this page is kept to resolve comments and will be archived.

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

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.

  • Implement scope in one or more alpha releases

TSC

  • Declare meta-release kickoff





M0 

Meta-release kickoff

M0

0

starts @ M0

Release Management

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

  • Once available, check the final alpha release of Commonalities & ICM and, if OK, submit to TSC for approval

  • After TSC approval, announce M1 milestone

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 releases

  • 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 final alpha release for Commonalities & ICM

  • Update the meta-release plan with the alpha release tag

TSC

  • Approve final 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 final release-candidate PR and submit to Release Management

  • 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 Commonalities and ICM final release-candidate PRs, announce M2 milestone

TSC

  • Approve final release-candidate PRs of Commonalities & ICM

7 weeks



M2

Release-candidate Commonalities & ICM

M1 + 7 weeks

9

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 to be released

  • Define scope of API release:

    • Record scope in dedicated GitHub issue.

    • Submit scope for TSC review

    • 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 API release-candidate PR

  • If OK, approve creation of first release-candidate

  • If NOK, or in case of questions, notify TSC for checking the API release-candidate PR

  • Announce M3 milestone with all approved API release-candidates.

TSC

  • Review API release-candidate PRs on request of Release Management and approve (or reject)

9 weeks



M3

Release-candidate APIs (Code Freeze)

M1 + 9 weeks

9

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 tag

Release Management

  • Once available, 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 proposed APIs

9 weeks



M4

Public-release APIs

M3 + 9 weeks

18

starts @ public-release PR for an API

Release Management

  • 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

  • Announce the M5 meta-release on all@lists.camaraproject.org 

TSC:

  • Meta-release approval

2 weeks



M5

Meta-release

M4 + 2 weeks

20

starts @ M5

Release Management

  • Review release process with all teams and identify areas for improvement. 

  • Propose improvements for TSC approval

TSC

  • Meta-release improvements approval.

2 weeks



M6

Post Release Assessment

M5 + 2 weeks

24