Attendees & Representation

Type @ and your name to indicate your attendance

Community: Akos Hunyadi

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

• #266 Align with commonalities r2.3

  • From the review of r2.2

• #263 Prepare release r2.2 for Spring25 M4

  • Review findings from Release Management have been fixed

• #262 Make lastStatusTime mandatory in 200 responses of the status APIs

Open issues

• #265 Align with Commonalities r2.3

  • PR is open

• #259 Create public release r2.2 for Spring25 M4

  • PR #255 needs to be closed before public release

  • Issues #258, #253 and #236 need to be closed before public release

• #258 Test statement for device-roaming-status & device-reachability-status APIs

  • One test statement from DT already posted in issue

  • Needs to be closed before public release r2.2

• #253 Create user story for device-roaming-status and device-reachability-status APIs

  • New PR required. Needs to be part of r2.2.

• #248 [device-reachability-status-subscriptions] Align functionality with the retrieve API

  • Tabled for discussion post current release

• #224 Scope for Spring25 release

  • Team decided to go for stable versions with device-roaming-status and device-reachability-status

• #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#138 How to respond if queried device does not have an active session?

  • Request documentation enhancement

• #119 How can a provider inform the ASP/aggregator about not implemented features in advance of the API call

  • 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 Nov 2024

Release candidate release r2.1 was published on 14 Feb 2025

DeviceDataVolume

Open PRs

• #13 Basic test specifications for both Device Data Volume and Its Subscription

Open Issues

• #16 Feedback on release r1.1 review

• #14 Error Response Code 422 missing- Device Data Volume

• #12 Create basic test specifications

• #11 Initial release r1.1

Release Management

DeviceQualityIndicator

Open PRs

• -

Open Issues

• #6 Create initial version

  • 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

• See Meta-release Spring25

• M3 (first release candidate) target date: 17 Jan 2025; publication date 14 Feb 2025

• M4 (public release) target date: 28.02.2025

AOB

Action items