Community Attendees:
...
Attendees & Representation
Type @ and your name to indicate your attendance
Community: Akos Hunyadi Sachin kumar Huub Appelboom Eric Murray Joachim Dahlgren Stefano Falsetto Fernando Prado Cabrillo Ludovic Robert
Agenda
Antitrust Policy
Action Items Review
DeviceStatus
Open pull requests
Open issues
Release Management
DeviceDataVolume
Open pull requests
Open issues
Release Management
DeviceQualityIndicator
Open pull requests
Open issues
Release Management
Meta Release
AOB
Minutes
DeviceStatus
Open PRs
...
#158 Create connected-network-type.yaml
Ready to be merged
Alignment of error codes with Commonalities 0.5.0 will be done in separate PR
#171 Create connected-network-type-subscriptions.yaml
...
Should be updated to align with #158
...
#237 Clarification for initialEvent use in documentation
To be extended for the new network-type-subscription API
#232 Update device error model
To be extended for the new network-type-subscription API
#231 Update device-reachability-status-subscriptions.yam
To be extended for the new network-type-subscription API
The datetime attributes should have quoted strings e.g. time: 2023-01-17T13:18:23.682Z => time: “2023-01-17T13:18:23.682Z”
The current description should be added to other APIs too
Open issues
To be extended for the new network-type-subscription API
Open for reviews
#171 Create connected-network-type-subscriptions.yaml
Has been merged during the call
Open issues
#238 Update example string values for properties defined with date-time format
#236 Create extended test cases for device-roaming-status and device-reachability-status
#230 Align Device Errors with last Commonalities agreement for Spring25
Corresponding PR is open
#224 Scope for Spring25 release
Team decided to go for stable versions with device-roaming-status and device-reachability-status
#222 Enhance API documentation
Ongoing discussion about the behavior with initialEvent in roaming-status-subscriptions
#220 Example Section Error: Status Should be "ACTIVE" for Synchronous Subscriptions
Should be fixed in next MR
Linked to 222 discussion
#212 Support of Multi-SIM lines in DeviceStatus APIs
Discussion still open in commonalities
Target release is Spring25, with a description how the APIs work in a multi-SIM setup
...
#143 Extend: Device Status Connectivity with Standard
PRs are open
Details about implementation should be provided
#138 How to respond if queried device does not have an active session?
Request documentation enhancement
no update
#115 /Connectivity API there is no indication for which particular subscriber event (DATA/SMS)
no update
Release Management
The patch release r1.3 was created on 05.11.2024.
DeviceDataVolume
Open PRs
...
Open Issues
...
Release Management
DeviceQualityIndicator
Open PRs
-
Open Issues
Known use case: client wants to decide, whether a quality boost should be triggered or not (is it worth?)
No API spec can be provided for Spring25, target is Fall25
Collect use cases
Release Management
Meta Release
Camara Meta Release spring 2025
M3 (first release candidate) target date:
...
17.
...
01.
...
2025
M4 (public release) target date: 28.02.2025
AOB
Next DeviceStatus call on
...
29.01.2025
Action items
...
- Akos Hunyadi Check for additional necessary (and missing) assets for the stable versions
...
- Fernando Prado Cabrillo Update #232
- Sachin kumar Update #231
- Eric Murray Update #228
- Ludovic Robert Update #237
- Akos Hunyadi Create DeviceStatus RC PR
- Akos Hunyadi Create PRs for the 2 Testing issues
- Akos Hunyadi DeviceDataVolume: check if DT needs it in Spring25 (feedback on Slack), if yes, an RC version is needed.