CAMARA release management process requires each API Sub-project to plan and track their API releases so that meta-release can be planned.
...
Meta-release | The name of the meta-release, e.g. Fall24 |
API name | The API name. See the definition of API name on this page: API Release Process, e.g. geofencing |
| Group | The name of the GitHub repository for the API Sub-project, e.g. DeviceLocation |
| Repository | The shortened link to GitHub repository for the API Sub-project, e.g. DeviceLocation |
| Target version | The API version that you plan to publish in the indicated meta-release, e.g. 1.0.0 |
| Target scope | The shortened link to a GitHub issue called "Scope for target version" which needs to be created latest at M1 and resolved by M3 e.g. DeviceLocation/issues/58 |
| Target maturity | Indicates the maturity of the API version that is targeted in the upcoming meta-release: choose one of initial / stable. |
| M3 date | The date when the latest alpha API version is ready. This is the starting point for creating the release-candidate API version for M4. After this date, only bug fixes and necessary non-breaking changes can be made to the API. Format is yyyy-mm-dd |
| M4 date | The date when the release-candidate API version for M5 submission is ready. This is the starting point for creating the public-release API version for M5. Once this date is provided by the API project team, the Release Management team can check the release-candidate API version for acceptance and submit to the TSC for approval. Format is yyyy-mm-dd |
| API version | The version of the latest pre-release (alpha or release-candidate) API version to be updated at M3 and M4 date, e.g. 0.2.0_alpha.3, 0.10.0-rc.2, 0.10.1, 1.0.0-rc.5) |
| pre-release tag | The shortened release tag of the latest pre-release (alpha or release-candidate) for the API version e.g. QualityOnDemand/releases/tag/r0.10 |
| M5 date | The date by which the Release Management team has checked the release-candidate API version provided at the M4 date and the API is approved by the TSC. The link to the PR for public-release API version shall be included in this field when available After this date, if approval is obtained, the API Sub-project shall commit the PR of the public-release API version and its release assets for use in the meta-release. Format is yyyy-mm-dd. The link to the PR shall be removed after the commit is done. |
| public-release tag | The shortened release tag of the public-release API version. This field is updated once the public-release has been created, e.g. QualityOnDemand/releases/tag/r1.0 |
| Comments | Any additional information on the API version, e.g. M4: API approved by TSC API release phase-out planned, retirement date planned, etc. Date format is yyyy-mm-dd. |
| Contacts | Contact names for the API release |
...
| Page Properties | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Nr | API release assets | alpha | release-candidate | public-release | |
initial | stable | ||||
1 | API definition |
|
|
|
|
2 | Design guidelines from Commonalities | N |
|
|
|
3 | Profile guidelines from ICM | N |
|
|
|
| 4 | API versioning conventions |
|
|
|
|
| 5 | Linting rules enabled |
|
|
|
|
6 | API documentation |
|
|
|
|
7 | User stories |
|
|
|
|
8 | Sunny day API test cases and documentation | N |
|
|
|
9 | Full set of API test cases and documentation | N | N |
|
|
10 | Test results (API test cases passed) | N |
|
|
|
11 | Security review |
|
|
|
|
12 | Maintainers (from at least 3 distinct companies) |
|
|
|
|
13 | Codeowners (from at least 3 distinct companies) |
|
|
|
|
14a | API release numbering conventions |
|
|
|
|
14b | Release notes according to template |
|
|
|
|
| 15 | Protected branches enabled |
|
|
|
|
16 | Release-candidate API version tested in at least 2 operator implementations | N | N |
|
|
17 | initial public-release API version certified and launched in at least 2 operators is needed to become stable | N | N | N |
|
...