Closed
Bug 1260065
Opened 8 years ago
Closed 8 years ago
Extend PLUGIN_ACTIVATION_COUNT telemetry probe expiration from FF 48 to 53
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(firefox45 unaffected, firefox46 unaffected, firefox47 unaffected, firefox48 fixed)
RESOLVED
FIXED
mozilla48
Tracking | Status | |
---|---|---|
firefox45 | --- | unaffected |
firefox46 | --- | unaffected |
firefox47 | --- | unaffected |
firefox48 | --- | fixed |
People
(Reporter: cpeterson, Assigned: cpeterson)
References
Details
Attachments
(1 file)
1.33 KB,
patch
|
benjamin
:
review+
qdot
:
feedback+
|
Details | Diff | Splinter Review |
The PLUGIN_ACTIVATION_COUNT telemetry probe expires in FF 48. FF 53 is the last Nightly version of 2016 and will hit the GA channel around April 2017. The choice of version 53 is somewhat arbitrary, but long enough to get us data through the beginning of next year.
Assignee | ||
Comment 1•8 years ago
|
||
Extend PLUGIN_ACTIVATION_COUNT telemetry probe expiration from FF 48 to 53. The PLUGIN_ACTIVATION_COUNT telemetry probe expires in FF 48. FF 53 is the last Nightly version of 2016 and will hit the GA channel around April 2017. The choice of version 53 is somewhat arbitrary, but long enough to get us data through the beginning of next year.
Attachment #8735313 -
Flags: review?(benjamin)
Attachment #8735313 -
Flags: feedback?(kyle)
Updated•8 years ago
|
Attachment #8735313 -
Flags: feedback?(kyle) → feedback+
Comment hidden (obsolete) |
Comment 3•8 years ago
|
||
The telemetry.mozilla.org dashboard only looks at users who have opted in to extended telemetry collection. To do comparative release numbers you need to run a custom query.
Updated•8 years ago
|
Attachment #8735313 -
Flags: review?(benjamin) → review+
Comment 5•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e7a1c3636af1
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•