...
Meta-release have 6 milestones, M0 through M6 described below. For the milestone dates per meta-release, please see the CAMARA Release Meta-release Roadmap.
The ongoing meta-release status is discussed in the Release Management working group meetings and recorded on the meta-release page.
...
- 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.
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 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.
Release packages
Release packages can be creates using the GitHub release process.
Each release package shall include the release notes using the provided template.
Each release package has a tag: pre-release or latest