Versions Compared

Old Version 56

changes.mady.by.user Tanja de Groot

Saved on

compared with

New Version 57

changes.mady.by.user Tanja de Groot

Saved on

Key

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

...

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

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

Release milestones and their associated tasks, are used to track the status of the meta-release. The milestones and management tasks used in the release process are described in the table below.

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

...

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.

Process

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

Details on API versioning and the link with the release management process is described here:  Planning and releasing API versions. Meta-release names will be named SpringYY or FallYY where YY is the (short) year number.

...

Releasing APIs. 

Release Management (M0, M5, M6)

...

The Release Management team has the following activities for each meta-release:

  • Create the meta-release page under CAMARA meta-releases
  • M0: Inform all team's release contacts through the release management mailing list that they need to create the API release tracker for their next planned API release as described here: How to track an API release.
  • Declare Request TSC to declare the kick-off of the meta release.
  • Starting at M4, : prepare and publish the meta-release at M5.
  • M5: Conduct a meta-release retrospective as input to the next meta release

...

  • Whenever a new pre-release is made available, the (Pre-)Release tag column shall be updated with the latest pre-release tag link for the API version.
  • The actual milestone dates shall be put in the table when the milestone is achieved. 
  • The link to the release package, when available, shall be added at each pre-release change, and at M2.
  • Once TSC approval is given at M2, the target public-release version shall be created for M5 and the meta-release page updated with the final public-release.

...

API Sub-projects (M0, M3, M4)

API Sub-project teams shall update their API release tracker for the API as follows: 

...