Problem description
This issue should serve for collecting topics to be addressed by next release of predictive-connectivity-data API:
Meta-release Fall26
Please add your proposals in the comments and open issues if needed.
A new label Sync26 has been defined to track all items in the predictive-connectivity-data Sync26 meta-release scope.
The WG should review as candidates those issues labeled with Sync26 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 |
Status |
| M1 (Commonalities & ICM) |
nov 30 |
from Spring26 |
| M0 |
jan 15 |
kick-off preparation |
| M2 (Commonalities & ICM) |
jan 31 feb 15 |
from Spring26 |
| M4 (Commonalities & ICM) |
mar 15 |
from Spring26 |
| M1 (API Sub Projects) |
apr 30 |
|
| M3 (API Sub Projects) |
jun 15 |
|
| M4 (API Sub Projects) |
sep 30 |
|
| M5 |
oct 15 |
|
| M6 |
oct 31 |
|
The scope for the PredictiveConnectivityData API should be defined until M1, leaving two month to create the release candidate
Expected action
Targets for Sync26 (proposed/to be discussed)
- Clarification and improvement of documentation
- Incorporation of feedback from implementations
- Alignment with Commonalities & ICM changes for Sync26
Target versions
- predictive-connectivity-data 0.2.0
Issues to be addressed in Sync26 scope
Potentially in scope, depending on Commonalities
Action Points
Auxiliary tasks:
Problem description
This issue should serve for collecting topics to be addressed by next release of predictive-connectivity-data API:
Meta-release Fall26
Please add your proposals in the comments and open issues if needed.
A new label Sync26 has been defined to track all items in the predictive-connectivity-data Sync26 meta-release scope.
The WG should review as candidates those issues labeled with Sync26 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.
The scope for the PredictiveConnectivityData API should be defined until M1, leaving two month to create the release candidate
Expected action
Targets for Sync26 (proposed/to be discussed)
Target versions
Issues to be addressed in Sync26 scope
Potentially in scope, depending on Commonalities
Action Points
Auxiliary tasks: