Remove or update probes expiring in Firefox 130: extensions.quarantinedDomains.list* before Gecko version gets increased to 130 on 2024-07-08
Categories
(WebExtensions :: General, task, P3)
Tracking
(firefox-esr115 unaffected, firefox127 unaffected, firefox128 unaffected, firefox129+ verified)
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox127 | --- | unaffected |
| firefox128 | --- | unaffected |
| firefox129 | + | verified |
People
(Reporter: telemetry-probes, Assigned: rpl)
References
Details
(Whiteboard: [probe-expiry-alert][addons-jira])
Attachments
(1 file)
The following Firefox probes will expire in the next major Firefox nightly release: version 130 [1].
extensions.quarantinedDomains.listsize
extensions.quarantinedDomains.listhash
extensions.quarantinedDomains.remotehash
What to do about this:
- 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).
- 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 #data-help 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.
Comment 1•1 year ago
|
||
At least toolkit/components/extensions/test/xpcshell/test_QuarantinedDomains_telemetry.js checks for this.
Comment 2•1 year ago
|
||
The bug is marked as tracked for firefox129 (nightly). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still isn't assigned.
:mixedpuppy, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
Comment 5•1 year ago
|
||
| bugherder | ||
Comment 7•1 year ago
|
||
Verified fixed with the latest version increase simulation.
Description
•