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.
Overview
CAMARA releases is scheduled to twice per year at approximately 6 month intervals (May and November). Releases are named after major world cities in alphabetical order. See the CAMARA Release Roadmap for a list of previous and future releases.
Releases are administered and tracked by a Community Release Managers. Release status is discussed at the << TBC >>
Release Milestones
Release milestones and their associated tasks, are used to track the status of the release. The milestones and management tasks used in the release process are described in the table below.
Milestone | Milestone Name | Description | Timeline |
---|---|---|---|
Kickoff - M0 | Start of release cycle. | M0 | |
M1 | Initiate Commonalities & ICM |
| M0 + 2 week |
M2 | Finalize Commonalities & ICM |
| M1 + 7 weeks |
M3 | Initiate Sub-Projects / APIs |
| M1 + 6 weeks |
M4 | Finalize Sub-projects / APIs |
| M3 + 8 weeks |
M5 | Meta Release |
| M4 + 2 weeks |
M6 | Post- Release |
| M5 + 2 weeks |
Meta-release content planning
For each meta-release, the respective teams shall update the information of what they plan to contribute on the relevant meta-release page.
Commonalities & ICM
The Commonalities and ICM teams shall respectively update the related table as follows:
- The version shall be updated with the latest pre-release version in use by the respective teams.
- The actual Mx dates shall be put in the table when the milestone is passed.
- The link to the release package shall be added 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 shall be updated with the latest pre-release API version in use by the team.
- The actual Mx dates shall be put in the table when the milestone is passed.
- The link to the release package shall be added 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.