...
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 is are scheduled to twice per year at approximately 6 month intervals (May March and NovemberSeptember). Releases Meta-releases are named after major world cities in alphabetical order. See the CAMARA Release Roadmap for a list of previous and future releases..
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 Releases are administered and tracked by a Community Release Managers. Release status is discussed at the << TBC >>
- 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.
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 nr | |
---|---|---|---|---|---|---|
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 |
Meta-release content planning
...