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

Compare with Current View Page History

« Previous Version 27 Next »

WIP

Introduction

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

Process

CAMARA meta-releases are scheduled twice per year at approximately 6 month intervals (March and September). Meta-releases are named after major world cities in alphabetical order.

Meta-release have 6 milestones, M0 through M6 described below. For the milestone dates per meta-release, please see the CAMARA Release Roadmap.

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 Sub-project Release Contacts (Maintainers) page.

The ongoing meta-release status is discussed in the Release Management working group meetings and recorded on the meta-release page.

The milestone status information is 

  • M0: meta-release preparation, kick-off
  • M1: scoped, work-in-progress
  • M2: release-candidate, released
  • M3: scoped, work-in-progress
  • M4: release-candidate, released
  • M5: meta-release finalization, published
  • M6: under retro, done

Release Milestones

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 NameDescriptionTimeline


Timeline

update

Week number

Kickoff - M0Start of release cycle.
M0
M00
M1Initiate Commonalities & ICM
  • Scope of Work Products clarified.
  • Identify commonalities work products.
  • Create initial PRs for commonalities.
  • Agree on the scope of commonalities.
  • TSC Approval.
M0 + 2 week
M0 + 2 week2
M2Finalize Commonalities & ICM
  • Release of Commonalities.
  • Complete initial PR reviews.
  • TSC Approval.
M1 + 7 weeks
M1 + 8 (+2) weeks12
M3Initiate Sub-Projects / APIs
  • Scope Request to Sub-Projects / APIs.
  • Determine requirements for 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.
  • Identify release candidates for sub-projects/APIs.
M1 + 6 weeks
M1 + 6 (+2) weeks10
 M4Finalize Sub-projects / APIs
  • Release of Sub-Projects / APIs.
  • Testing & Acceptance.
  • Conduct testing.
  • Evaluate acceptance criteria.
  • Code Freeze
M3 + 8 (+2) weeks
M3 + 8 (+2) weeks20
M5Meta Release
  • Bundle & publish release
  • Common Release Date ("packaging done for the community release").
M4 + 2 weeks
M4 + 2 weeks22
M6Post- Release
  • Review release process and identify areas for improvement. 
  • Release Retro.
    • Inputs from Sub Projects
  • TSC Approval.
M5 + 2 weeks
M5 + 2 weeks24

Meta-release content planning & status

The below teams shall update the relevant meta-release page with the information of what they plan to contribute to the meta-release, and with the status updates during the meta-release cycle.

Commonalities & ICM

The Commonalities and ICM teams shall respectively update the related table as follows:

  • The Version column shall be updated with the latest pre-release version in use by the respective teams.
  • The actual milestone dates shall be put in the table when the milestone is passed. 
  • The link to the release package shall be added at each version change, and at M2 (and is the same at M5).
  • When M2 is passed, the target public-release version shall be put in the Version column.

APIs

API Sub-project teams shall update the table for APIs as follows: 

  • The Version column shall be updated with the latest pre-release API version in use by the team.
  • The actual milestone dates shall be put in the table when the milestone is passed. 
  • The link to the release package shall be added at each version change, and minimally at M3, M4, and the final at M5.
  • When M5 is passed, the target public-release API version shall be put in the Version column.


  • No labels