WIP
| Table of Contents |
|---|
Introduction
A CAMARA meta-release is the way CAMARA brings its APIs to market.
A meta-release consists of a set of public versions of curated APIs that went though the CAMARA meta-release process.
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.
define
- the milestones of the meta-release (this page), and the supporting Meta-release Process documentation
- the activities expected from the different teams to move from one milestone to the next
- the way to report progress on the meta-release itself, on the Commonalities and ICM releases and on API releases
For the schedule and content of actual planned meta-releases, see CAMARA meta-releases.
Meta-release milestones
Meta-release milestones and their associated actions are used to progress and track the status of the meta-release.
...
- 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 milestones and their associated tasks, are used to track the status of The following table lists the meta-release . The milestones and management tasks used in the release process are described in the table below., and includes a high level view of the activities expected from the various teams to reach these milestones.
More details on these for each team are documented here:
- Commonalities, ICM: release tracking and milestone activities
- API Sub Projects: release tracking and milestone activities
- Release Management: meta-release tracking and milestone activities
- TSC: milestone activities
| Milestone / start date | Actors & Activities for next |
|---|
milestone | Timeline | Week |
|---|
Nr |
|---|
| pre-M0 |
| activities |
| ||
| M0 | Meta-release kickoff | M0 | 0 |
| activities for M1 start @ M0 |
|
- 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.
| 2 weeks | ||
M1 | Alpha Commonalities & ICM | M0 + 2 weeks | 2 |
| activities for M2 start @ M1 |
| 7 weeks | |
M2 | Release-candidate Commonalities & ICM | M1 + 7 weeks | 9 |
| activities for M3 start @ M1 |
| 9 weeks | |
M3 | Release-candidate APIs (Code Freeze) | M1 + 9 weeks | 9 |
| activities for M4 start @ M3 |
| 9 weeks | |
M4 | Public-release APIs | M3 + 9 weeks | 18 |
activities for M5 starts @ public-release PR for an API |
| 2 weeks | |
M5 | Meta |
M2
- Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
M3
- 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
M4
- 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
M5
| -release | M4 + 2 weeks |
| 20 |
| activities for M6 |
- Review release process and identify areas for improvement.
- Release Retro.
- Inputs from Sub Projects
- TSC Approval.
Meta-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.
| start @ M5 |
| 2 weeks | |
M6 | Post Release Assessment | M5 + 2 weeks | 24 |
...
Processes
All CAMARA teams play their part in the meta-release process. This section describes the action of each team.. An overview of the activities per team is shown in the above table.
The details on the activities for each team can be found in the below process descriptions:
- The process to manage a meta-release roadmap is described described here: Meta-Release Processrelease Process
- The process for the Commonalities and ICM teams is described here: Commonalities and ICM release process
- Details on releasing an API version and the related related API versioning are described here: API Release Process.
...