Summary
Three data quality anomalies were found in releases-master.yaml while working on the Progress Tracker. The Release Collector (which populates that file) should be investigated to determine whether these are input errors or collector bugs, and validated/corrected accordingly.
Anomalies found
1. EnergyFootprintNotification – API renamed between RC and public-release (Fall25)
The RC release (r1.2) uses api_name: energy-footprint, but the public-release uses api_name: energy-footprint-notification. If the rename happened during the cycle, the RC entry in releases-master.yaml may be correct as-is. However, this should be confirmed and documented.
Impact: Progress Tracker milestone count for Fall25 was off by 1 (M3 for this repo not counted correctly before the fix to use repo-level counting).
2. ConnectivityInsights – Malformed api_name in RC (Fall24)
The RC release entry contains api_name: v0.4rc1 which appears to be a version string accidentally used as an API name instead of connectivity-insights-subscriptions.
Impact: Progress Tracker milestone count for Fall24 was off by 1 (api_version lookup for this API name failed).
Likely action: Correct the api_name in the RC entry in releases-master.yaml to connectivity-insights-subscriptions (if that was the intended value at the time of the RC).
3. RegionDeviceCount – Missing api data in r1.1 and r1.2 (Spring25)
Releases r1.1 (pre-release-alpha) and r1.2 (public-release) have no apis: entries in releases-master.yaml. Only r1.3 (maintenance-release) has the api data (region-device-count: 0.1.0).
Impact: Progress Tracker showed a placeholder (RegionDeviceCount) instead of the api name for the Spring25 historical entry.
Likely action: Backfill api data for r1.1 and r1.2 in releases-master.yaml, or confirm this was a known gap in the Release Collector at the time of those releases.
Suggested collector improvements
- Add a validation step that warns when an RC api_name does not appear in any other release for the same repo/cycle (catches renames and typos).
- Add a check that at least one non-maintenance release in a cycle has api data, and warn if none do.
Related
Progress Tracker PR: #186
Summary
Three data quality anomalies were found in
releases-master.yamlwhile working on the Progress Tracker. The Release Collector (which populates that file) should be investigated to determine whether these are input errors or collector bugs, and validated/corrected accordingly.Anomalies found
1. EnergyFootprintNotification – API renamed between RC and public-release (Fall25)
The RC release (
r1.2) usesapi_name: energy-footprint, but the public-release usesapi_name: energy-footprint-notification. If the rename happened during the cycle, the RC entry in releases-master.yaml may be correct as-is. However, this should be confirmed and documented.Impact: Progress Tracker milestone count for Fall25 was off by 1 (M3 for this repo not counted correctly before the fix to use repo-level counting).
2. ConnectivityInsights – Malformed api_name in RC (Fall24)
The RC release entry contains
api_name: v0.4rc1which appears to be a version string accidentally used as an API name instead ofconnectivity-insights-subscriptions.Impact: Progress Tracker milestone count for Fall24 was off by 1 (api_version lookup for this API name failed).
Likely action: Correct the api_name in the RC entry in releases-master.yaml to
connectivity-insights-subscriptions(if that was the intended value at the time of the RC).3. RegionDeviceCount – Missing api data in r1.1 and r1.2 (Spring25)
Releases
r1.1(pre-release-alpha) andr1.2(public-release) have noapis:entries in releases-master.yaml. Onlyr1.3(maintenance-release) has the api data (region-device-count: 0.1.0).Impact: Progress Tracker showed a placeholder
(RegionDeviceCount)instead of the api name for the Spring25 historical entry.Likely action: Backfill api data for r1.1 and r1.2 in releases-master.yaml, or confirm this was a known gap in the Release Collector at the time of those releases.
Suggested collector improvements
Related
Progress Tracker PR: #186