API release trackers provide visibility on the development of an API version to the wider CAMARA community and beyond. A tracker can be created for any API version, whether planned for the meta-release or not.
If not planned to be part of the meta-release, remove the page label “camara-springxx/fallxx”, and add the label “camara-other”.
| Page Properties |
|---|
Meta-release | Spring25 | choose one | API name | connected-network-type | API name in lower-kebab-case | Target version | 0.1.0 | major.minor.patch version. Do NOT update with patch version | Repository | DeviceStatus | short link to API repository | Group | DeviceStatus | short link to Sandbox/Sub-Project Confluence wiki home page | Maturity | initial | choose one | Scope | DeviceStatus Spring25 scope | short link to API scope GitHub issue (Repository/issues/nr) | API version | - | OAS definition version field of the last (pre-)release. Update with patch release | M3 date | yyyy-mm-dd | update mandatory with final M3 pre-release date | Pre-release | <short tag link> | update with each alpha and rc pre-release tag | M4 date | yyyy-mm-dd | update mandatory with M4 public release date | Public release | <short tag link> | update with M4 public release tag or patch release tag | Patch date | | update with each patch release date, if applicable | RM reviews | <issue link(s)> | RM review issue link(s). Add for M3 and M4. | Comments | free text | | New | yes | choose one. Use yes if it is the first time the API is part of a meta-release, else use no. | Contacts | Akos Hunyadi Ludovic Robert | use @name format |
|
For guidelines on how to fill the table, see here: API release trackers
Add any other useful information about the API version here.