This section gives an the overview of the proposed handling of API versions and their handling in the release management process.Highlights of the proposal
Synthesis:
- Use of CAMARA internal initial or alpha (-alpha.m) API versions (with version extensions) are used for CAMARA internal API development management purposes
- Use of CAMARA internal release-candidate (-rc.n) API versions (with version extensions) are used for CAMARA internal API release management purposes
- Externally released APIs (Use of public-release API versions are used for API versions that are part of a meta-release) . These API versions only have API version number x.y.z (semver 2.0), no version extension.
- People are free to use initial, alpha or release-candidate API versions available in the CAMARA GitHub at their own risk.
- API families are not versioned, nor release-managed, only API versions are release-managed.
- API versions are created by putting a version tags on the main or on a release branch (in case of evolution of released APIs).
- API release are created by putting a release tag on the main or on a release branch (in case of evolution of released APIs), and by creating a GitHub release package.
The following sections provide the details on definitions and the processes, and illustrates by examples.
It consolidates inputs from
...