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 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 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 Process.
Release milestones and their associated actions are used to progress and track the status of the meta-release.
The actions required from the various teams in the release process are described in the table below.
NOTE: alternate table format proposed under review here: FOR REVIEW: Updated table of CAMARA Release Process - CAMARA Project - Confluence
The following table lists the meta-release milestones, 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 |
| 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 |
Timeline
Week number
M1
- 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.
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.
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 or put the release contact on their API release trackers.
Team release contacts need to subscribe to the release management mailing list.
All communication on an ongoing meta-release and its progress will be managed through this mailing list.
start @ M5 |
| 2 weeks | |
M6 | Post Release Assessment | M5 + 2 weeks | 24 |
Processes
All CAMARA teams play their part in the meta-release process. The actions are listed An overview of the activities per team is shown in the above milestone table.
Additional information The details on the actions activities for all teams each team can be found in the below process descriptions:
- The process to manage a meta-release is described here: Meta-release 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 API versioning are described here: API Release Process.
...