...
The purpose of this document is to describe the cadence, processes, milestones, and associated tasks used in the CAMARA release cycle. See CAMARA metaMeta-releases for information and schedule for specific releases.
...
- 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.
For sub-projects that contain multiple APIs in separate files,
- A folder per API shall be created for its development.
- The meta-release page shall list the individual APIs in the table with the version considered in the meta-release.
- The API version used in the API release asset naming is TBC.
Release branches
the main branch always contains the latest API version. It is meant for development.
API versions can be frozen in a work-in-progress pre-release branch or in a release-candidate pre-release branch. These These pre-releases become more stable with increasing pre-release numbers.
- Each pre-release branch has a pre-release tag.
- Considering an API Family with more APIs inside, a Release Tag and a new Release Branch is done when all the APIs are completed.
...