Versions Compared

Old Version 60

changes.mady.by.user Tanja de Groot

Saved on

compared with

New Version 61

changes.mady.by.user Tanja de Groot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

WIP

Table of Contents

Introduction

The purpose of this document is to describe the cadence, processes, milestones, and associated tasks used in the CAMARA meta-release cycle.

See CAMARA meta-releases for information and schedule of planned 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 Planning.

...

MilestoneMilestone NameActions to achieve milestone

Timeline

Week number

Kickoff - M0Start of meta-release cycle.
M00

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 week2

M2

Finalize Commonalities & ICM
  • Create release-candidate for Commonalities & ICM
  • Prepare public-release for Commonalities & ICM.
  • Complete initial PR reviews.
  • TSC Approval.
M1 + 10 weeks12

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 weeks22

M6

Post- Release
  • Review release process and identify areas for improvement. 
  • Release Retro.
    • Inputs from Sub Projects
  • TSC Approval.
M5 + 2 weeks24

Release cadence

CAMARA meta-releases are scheduled twice per year at approximately 6 month intervals (March and September). 

Meta-releases are named SpringYY or FallYY respectively, where YY is the (short) year number. For example Fall24, Spring25, Fall25, etc.

Release contacts 

Meta-releases are administered and tracked by

...

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

Processes

All CAMARA teams play their part in the meta-release process. This section describes the action of each team.

...