...
The Release Management process is based on API versions and their associated release assets. It uses
- work-in-progress API version is used during the development of an the API. This versions is not considered as release and is not usable by API consumers.
- initial or alpha (-alpha.m) API versions (with version extensions) are used for CAMARA internal API development purposes
- release-candidate (-rc.n) API versions (with version extensions) are used for CAMARA internal API release management purposes
- 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.
- An API versions are version release is identified by putting an API version tags tag on the main or on a release branch (the latter in case of changes to a public-released APIsAPI).
- An API release consists in creating the related set of API version assets and delivering them in an API version release package.
- Note 1: People are free to use initial, alpha or release-candidate API versions available in the CAMARA GitHub at their own risk.
- Note 2: API families are not versioned, nor release-managed, only . Only API versions are release-managed.
...