...
- Use of CAMARA internal alpha (-alpha.m) API versions (with version extensions) for API development management purposes
- Use of CAMARA internal and release-candidate (-rc.n) API versions (with version extensions) for release management purposesNo use of alpha or beta extensions (internal nor external to CAMARA) as no clear definition is identified.
- Externally released APIs (public-release API versions of a meta-release) only have API version number x.y.z (semver 2.0), no version extension
- People are free to use prealpha or release-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.
It consolidates inputs from
- Rafal's proposal for the CAMARA API Maturity Levels - proposal - CAMARA Project - Confluence. and Herbert's comments
- the inputs from Consolidation Issue for open points release management · Issue #9 · camaraproject/ReleaseManagement (github.com).
- Proposal to establish API Families as Working Groups across API Sub Projects · Issue #7 · camaraproject/ReleaseManagement (github.com)
- Open Issues Consolidated - CAMARA Project - Confluence
This page was briefly discussed on the RM call of 2024-03-1926. Initial feedback Feedback was:
- use work in progress alpha "-alpha.m" API version shall not be considered as a pre-release, but a not-released.
- release-candidate n" and release candidate "-rc.n" extensions
- these extension only instead of alpha and beta as the latter are not easy to define. These extensions should be only used internally in CAMARA for release management, but not in externally released APIs, which should only have semver numbers.
- API implementers are free to use these pre-release versions as they see fit, but there is no guarantee from CAMARA side that they will not change. recommended to start implementation of the API with the first release-candidate API version in order to gove feedback on the API definition. The API definition may change following API implementation feedback on the release-candidate, and result in an updated release candidate.
- Only fully tested release candidiates can become part of a meta-release.
Table of Contents
| Table of Contents |
|---|
...