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”.
Meta-release | Spring25 | choose one | API name | geofencing-subscriptions | API name in lower-kebab-case | Target version | v0.4.0 | major.minor.patch version. Do NOT update with patch version | Repository | DeviceLocation | short link to API repository | Group | DeviceLocation | short link to Sandbox/Sub-Project Confluence wiki home page | Maturity | initial | choose one | Scope | DeviceLocation/issues/280 | short link to API scope GitHub issue (Repository/issues/nr) | API version | 0.4.0 | OAS definition version field of the last (pre-)release. Update with patch release | M3 date | 2025-02-05 | update mandatory with final M3 pre-release date | Pre-release | r2.1 | update with each alpha and rc pre-release tag | M4 date | 2025-03-10 | update mandatory with M4 public release date | Public release | r2.2 | update with M4 public release tag or patch release tag | Patch date | | update with each patch release date, if applicable | RM reviews | M3: #147 - ok M4: #181 - ok | RM review issue link(s). Add for M3 and M4. | Comments | free text | | New | no | choose one. Use yes if it is the first time the API is part of a meta-release, else use no. | Contacts | Jose Luis Urien Pinedo Ludovic Robert Maximilian Laue | use @name format |
|
For guidelines on how to fill the table, see here: API release trackers
Additional Information
Add any other useful information about the API version here.