...
| Info |
|---|
Please note that initial public API versions can be
|
- An A public API version is released only if it provides all required API readiness checklist items (see: [API Readiness Checklist](https://wiki.camaraproject.org/display/CAM/API+Release+Process#APIReleaseProcess-APIreadinesschecklist).
- Stable public API versions are recommended for use in commercial applications. The user can expect that subsequent public API versions will be backward-compatible with the one they are using, unless explicitly announced otherwise.
Meta-release
When planning to deliver a public API version into To be part of a meta-release, the API Sub Project needs to participate in the meta-release process. (Pre-)releases need For the meta-release, the following needs to be provided as follows:
- the API release tracker (see [API release trackers](https://wiki.camaraproject.org/x/HQBFAQ))
- the expected (pre-)releases need to be provided at the respective M3 and M4 milestones
- minimally an initial public release needs to be provided for the meta-release.API version
- each (pre-)release must include the required set of API release assets according to the API readiness checklist (see below).
- API (pre-)releases are numbered (tagged) using the API release numbering guideline (see below).
Example of the use of the API release process
...
| release type | API version | release number (release tag) | release package | release package taglabel |
|---|---|---|---|---|
| N/A | work-in-progress | N/A | N/A | N/A |
| pre-release | alpha | rx.1 ... rx.m | optional | optional: "pre-release" |
| pre-release | release-candidate | rx.m+1 ... rx.n | mandatory | "pre-release" |
| release | public | rx.n+1 | mandatory | "latest" |
| maintenance release | public | rx.n+2 ... rx.n+p | mandatory | "latest" |
...