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.
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.
Milestone | Milestone Name | Description | Timeline | Timeline update | Week number | |
---|---|---|---|---|---|---|
Kickoff - M0 | Start of release cycle. | M0 | M0 | 0 | ||
M1 | Initiate Commonalities & ICM |
| M0 + 2 week | M0 + 2 week | 2 | |
M2 | Finalize Commonalities & ICM |
| M1 + 7 weeks | M1 + 8 (+2) weeks | 12 | |
M3 | Initiate Sub-Projects / APIs |
| M1 + 6 weeks | M1 + 6 (+2) weeks | 10 | |
M4 | Finalize Sub-projects / APIs |
| M3 + 8 (+2) weeks | M3 + 8 (+2) weeks | 20 | |
M5 | Meta Release |
| M4 + 2 weeks | M4 + 2 weeks | 22 | |
M6 | Post- Release |
| M5 + 2 weeks | M5 + 2 weeks | 24 |
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.
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 Sub-project Release Contacts (Maintainers) page.
Release milestones & status
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
Meta-release
- Create the meta-release page
- Inform the teams through the release management mailing list that they need to provide input to the meta-release page.
- Declare the kick-off of the meta release
The below teams shall update the 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.