Meta-release Milestones (old table)

Owned by Tanja de Groot
May 01, 2024
2 min read

WIP

Introduction

The purpose of this document is to describe the milestones and expected tasks. It references the supporting processes used in the CAMARA meta-release cycle.

For the schedule and content of planned meta-releases, see CAMARA meta-releases.

Meta-release Milestones

A meta-release has 6 milestones, M0 through M6 described below. For the typical milestone dates of a meta-release, please see theย Meta-release Process.

Release milestones and their associated actions are used to progress and track the status of the meta-release.

The actions required from the various teams in the release process are described in the table below.

NOTE: alternate table format proposed under review here: FOR REVIEW: Updated table of CAMARA Release Process - CAMARA Project - Confluence

Milestone

Milestone Name

Actions to achieve milestone

Timeline

Week number

Milestone

Milestone Name

Actions to achieve milestone

Timeline

Week number

Kickoff - M0

Start of meta-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

Release contactsย 

Meta-releases are administered and tracked by

  • the CAMARA Release Managers, supported by

  • the release contacts of the Commonalities and ICM working groupsย 

  • the release contacts of the API Sub-projects

The teams can put their release contact names on the Release Contacts page or put the release contact on their API release trackers.

Team release contacts need to subscribe to the release management mailing list.

All communication on an ongoing meta-release and its progress will be managed through this mailing list.

Processes

All CAMARA teams play their part in the meta-release process. The actions are listed in the above milestone table.

Additional information on the actions for all teams can be found in the below process descriptions: