New meta-release milestone table

Owned by Tanja de Groot
Last updated: May 18, 2024
4 min read

NEW PROPOSAL



Milestone / start date

Actors & Activities for next milestone

Timeline

Week Nr

Milestone / start date

Actors & Activities for next milestone

Timeline

Week Nr

pre-M0

  • Release Management: prepare meta-release plan

  • Commonalities & ICM: define scope and start alpha release development

  • TSC: declare M0 - meta-release kickoff





M0ย 

Meta-release kickoff

M0

0

starts @ M0

  • 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

2 weeks



M1

Alpha Commonalities & ICM

M0 + 2 weeks

2

starts @ M1

  • API Sub Groups: align to Commonalities and ICM alpha release and provide feedback

  • Commonalities & ICM: Fix bugs and prepare final release-candidate for M2

  • TSC: approve Commonalities and ICM final release-candidate

  • Release Management; declare M2 - Commonalities and ICM release-candidate available

7 weeks



M2

Release-candidate Commonalities & ICM

M1 + 7 weeks

9

starts @ M1

  • API Sub 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 available

9 weeks



M3

Release-candidate APIs (Code Freeze)

M1 + 9 weeks

9

starts @ M3

  • 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

9 weeks



M4

Public-release APIs

M3 + 9 weeks

18

starts @ public-release PR for an API

  • Release Management: prepare and declare M5 - meta-release availability

  • TSC: approve meta-release for M5

2 weeks



M5

Meta-release

M4 + 2 weeks

20

starts @ M5

  • 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

2 weeks



M6

Post Release Assessment

M5 + 2 weeks

24





ORIGINAL TABLE

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

  • Starting from previous M2, prepare scope definition for upcoming 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

  • Announce M0 meta-release kick-off on all@lists.camaraproject.org

  • Once available, check the final alpha releases PR 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

API Sub Projects

  • Start following the scope definitions of Commonalities and ICM and assess impact on API version

TSC

  • Approve Commonalities and ICM scope

  • 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

  • Assess final impact of final release-candidates of Commonalities and ICM scope on API(s)

  • 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 releases

  • 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

  • Review scope of selected APIs (case by case selection)

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 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, for each API

  • Once available, check final API release-candidate PR and, if OK, approve PR

  • Once available, check API public-release PR, and, if OK, ask for formal TSC approval.ย 

  • 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 Release Management check and 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

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 with their public-release tag 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

  • After TSC approval, announce M6 milestone

TSC

  • Provide feedback on meta-release

  • Meta-release improvements approval.

2 weeks



M6

Post Release Assessment

M5 + 2 weeks

24

Pro