customer-insights v0.2.0
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 | Fall25 | The name of the meta-release, e.g. Springxx or Fallxx. Put N/A if the API version is planned to be an initial public version only outside of the meta-release. |
API name | customer-insights | The API name. For the definition of "API name" on this page see: API Release Process, e.g. geofencing |
Target version | 0.2.0 | The API version that you plan to publish in the meta-release, e.g. 0.5.0, 1.0.0, 1.1.0, etc. Note: patch versions of a released API are handled on the same release tracker as the released API. |
Repository | The short link to GitHub repository for the API, e.g. DeviceLocation | |
Group | The name of the API Sandbox or Sub project under which the repository of the API is managed, e.g. DeviceLocation | |
Maturity | initial | Indicates the maturity of the public API version that is targeted in the upcoming meta-release: choose one of "initial" or "stable". |
Scope | The shortened link to a GitHub issue called "Scope for API-name version <x.y.z>" which needs to be created latest at M1 and resolved by M3 e.g. DeviceLocation/issues/58 | |
API version | 0.2.0 | The version of the latest (pre-)release (alpha, release-candidate or public release) API version. This field is to be updated with each (pre-)release date, e.g. 0.2.0-alpha.3, 0.10.0-rc.2, 0.10.1, 1.0.0-rc.5, etc.) |
M3 date | 2025-07-11 | This is the actual date of the M3 pre-release of the API version. Update of this field is mandatory with the final M3 pre-release creation date. Format is yyyy-mm-dd. |
Pre-release | The short link to the release tag, updated with each alpha and release-candidate pre-release. | |
M4 date | 2025-09-11 | This is the actual date of the M4 public-release of the API version. Update of this field is mandatory with the final M4 public-release creation date. Format is yyyy-mm-dd. |
Public release | The short link to the release tag, updated with the M4 public release and with every public maintenance release, including maintenance releases. | |
Patch date |
| The date of the availability of a maintenance release (after M4). Format is yyyy-mm-dd. |
RM reviews | M3: #252 ok M4: #290 ok | Review status and short link to the review issue for the M3 and M4 milestone release PR reviews: e.g. M4: OK ReleaseManagement/issues/88 M3: OK ReleaseManagement/issues/73 Any other reviews or relevant info. |
Comments |
| Comments on the API e.g. Previous API version(s) implemented by China Unicom, China Telecom, Vivo (Brazil), Deutsche Telekom (Germany), T-Mobile US, Telefonica (Spain). GSMA certified implementations by China Unicom. (source: https://www.open-gateway.com/operators-map as of 2024-08-16) |
New | no | yes | no - Choose one. Use yes if it is the first time the API is part of a meta-release, no otherwise. |
Contacts | @Pedro Díez García | Contact names for the API release: name1 @name2 |
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.