PR#36

Admin: migrate to centralized linting workflows - This pull request migrates this repository from local linting configuration to centralized linting workflows managed by the CAMARA project.

N/A

#32

Alignment with Commonalities r3.3 - Commonalities r3.3 introduces new changes that didn't appear in r3.2, which were the guidelines for PredictiveConnectivityData r1.1

N/A

#9

Scope for Fall25 releases (in preparation) - Release tracker management, alignment with transversal, API readiness checklist, functional enhancements and testing enhancements.

N/A

PR#26

Add “Best Effort” Service Level - Introduce a BEST_EFFORT service level providing qualitative coverage predictions without guaranteeing specific service levels.

• There’s an ongoing discussion around introducing a BEST_EFFORT service level, focusing on how to map qualitative coverage assessments to existing connectivity levels (GC, MC, NC, ND) without defined KPIs or thresholds.

  • Current PR

#35

Add User Stories for Predictive Connectivity Data API - The Predictive Connectivity Data API currently does not have documented User Stories, which are mandatory for stable public releases. The current status of the API is initial and not a priority, but it is a task that would be good to move forward with.

• In progress

#34

Release r1.2 (Fall'25 M4) - Publication of Fall'25 M4 public release of predictive-connectivity-data v0.1.0

• Under review by the Release Management WG

  • #38: Issue from Release Management:
    The asynchronous response in PredictiveConnectivityData does not comply with Commonalities r3.3 (uses application/json instead of CloudEvents).

     

    Decision: proceed with Fall’25 RC as is, create issues, document the exception in the API Readiness Checklist, and fix in v0.2.0 (post-Fall’25, dual-phase).