Scope for Fall25 releases (in preparation) #9
Description
Problem description
This issue should serve for collecting topics to be addressed by next release of predictive-connectivity-data API:
Meta-release Fall25
Please add your proposals in the comments and open issues if needed.
A new label fall25 has been defined to track all items in the device swap Fall25 meta-release scope.
The WG should review as candidates those issues labeled with fall25 to decide whether to include or discard them (at least for now). And WG participants can submit new proposals for the next release to be considered as well.
| Milestone | Target Date | Target Status |
|---|---|---|
| M1 | April 15 | Commonalities & ICM alpha release (proposal to TSC on apr 3rd to shift the M1 date to apr 29) |
| M2 | 7 June | Commonalities & ICM release candidate |
| M3 | June 21 | Alpha Release |
| M4 | August 31 | Release Candidate |
| M5 | September 15 | Meta Release |
| M6 | September 30 | Retrospective |
The scope for the PredictiveConnectivityData API should be defined until M1, leaving two month to create the release candidate
Expected action
Targets for Fall25 (proposed/to be discussed)
- Clarification and improvement of documentation
- Incorporation of feedback from implementations
- Alignment with Commonalities & ICM changes for Fall25
Target versions
- predictive-connectivity-data TBD
Issues to be addressed in Fall25 scope
- Allow output to include Signal Strength (in addition to Service Level) #8
- Support precision as an input parameter #7
- Support height as an input parameter #6
Potentially in scope, depending on Commonalities
N/A
Further (backlog) issues under discussion for Fall25
N/A
No business requirements known, not in scope:
N/A