You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 59 Next »

WIP

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.

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

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

  • 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 (Maintainers) page.

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 releasing API and the related API versioning are described here: API Release Process. 

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: API release trackers.
  • Request TSC to declare the kick-off of the meta release.
  • M4: prepare and publish the meta-release at M5.
  • M5: Conduct a meta-release retrospective as input to the next meta release

At M0 preparation,

  • the Commonalities and ICM teams shall update the applicable meta-release page with the scope definition of what they plan to put in the meta-release.
  • all API Sub-project teams shall create their release tracker page(s) for the API version(s) they plan to contribute to the meta-release.

The status of the ongoing meta-release is discussed in the Release Management working group meetings.

Meta-release progress is visible on the meta-release page created for each meta-release. The data is obtained as follows:

  • the Commonalities and ICM data is updated directly on the meta-release page by the respective teams.
  • the API data is managed by the API Sub-project teams on their API release tracker page(s) and pulled into the meta-release page automatically.

Release milestone status

The milestone status values are defined as follows:

MilestoneBefore M dataAfter M date
M0scope definitionkick-off done
M1wip / alphaalpha available for M2
M2wip / release-candidaterelease-candidate available for M3
M3API wip / alphaAPI alpha available for M4
M4API wip / release-candidateAPI release-candidate available for M5
M5meta-release preparationmeta-release published
M6retrospective ongoingmeta-release concluded

Commonalities & ICM (M0, M1, M2)

The Commonalities and ICM teams shall respectively update the related meta-release page table as follows:

  • 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 Commonalities and ICM version respectively.
  • 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. The API Sub-projects shall work with the pre-release provided at M2.

API Sub-projects (M0, M3, M4)

API Sub-project teams shall create and update the API release tracker for each of their API(s) as follows: 

  • With the each alpha or release-candidate API version, the API version and release tag shall be updated, and minimally at M3 and M4.
  • The actual milestone dates shall be put in the release tracker when the milestone is passed.
  • When M5 is passed, the link to the public-release API package shall be added.

Meta-release planning

The process to manage a meta-release roadmaps be found here: Meta-Release Planning


  • No labels