Closed Bug 1645087 Opened 5 years ago Closed 5 years ago

Remove or update probes expiring in Firefox 80: a11y.theme

Categories

(Firefox :: Disability Access, task)

task

Tracking

()

RESOLVED FIXED

People

(Reporter: telemetry-probes, Unassigned)

References

Details

(Whiteboard: [probe-expiry-alert])

The following Firefox probes will expire in the next major Firefox nightly release: version 80 [1].

a11y.theme

What to do about this:

  1. If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
  2. If one, some, or all of the metrics are still required, please submit a Data Collection Review [2] and patch to extend their expiry. There is a shorter form for data collection renewal [3].

If you have any problems, please ask for help on the #fx-metrics Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.

Your Friendly, Neighborhood Telemetry Team

[1] https://wiki.mozilla.org/Release_Management/Calendar
[2] https://wiki.mozilla.org/Firefox/Data_Collection
[3] https://github.com/mozilla/data-review/blob/master/renewal_request.md

This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: General → Disability Access APIs
Product: Firefox → Core

Morgan, I assume we only extended this to 80 due to that debacle with the automated tests? If we still want this, we're going to need to deal with this in one way or another for 80.

Asa, we do still want this, right? My feeling is yes.

Component: Disability Access APIs → Disability Access
Flags: needinfo?(mreschenberg)
Flags: needinfo?(asa)
Product: Core → Firefox

This tells us if a user has Windows HCM enabled? If so, yes, we still want this.

Flags: needinfo?(asa)

Oops, with all the back and forth on the test in bug 1630391 I forgot to adjust the expiry once it landed. I'll take care of this :)

Flags: needinfo?(mreschenberg)

oh wait, no I didn't... Am I missing something? Looks like both a11y.theme and a11y.backplate are set to never expire: https://searchfox.org/mozilla-central/rev/9b282b34b5aa0f836beb735656c55efb2cc4c617/toolkit/components/telemetry/Scalars.yaml#73

Flags: needinfo?(jteh)

So they are. I... don't know what's going on. 🤷‍♂️

Comment 0 says we should ask for help on the #telemetry Matrix room if we run into problems. Do you mind following that up? Seems like this is probably bogus, but it'd be good to know why it's been flagged.

Flags: needinfo?(jteh) → needinfo?(mreschenberg)

Asked in #telemetry, will update :)

Flags: needinfo?(mreschenberg)

ni'ing bewu because he wrote the auto-nag script for telemetry, according to wlach

Flags: needinfo?(bewu)

Looks like that change to expiry was made the day after this bug was filed so it was still valid at the time. Bugs aren't automatically closed though so you can close it now.

Flags: needinfo?(bewu)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.