Confirmed users
534
edits
(update) |
(→Update 2016-10: Update) |
||
| Line 3: | Line 3: | ||
This page documents the efforts to measure Go Faster deployments. This is currently in the discovering phase. | This page documents the efforts to measure Go Faster deployments. This is currently in the discovering phase. | ||
= Update 2016-10 = | = Update 2016-10-20 = | ||
'''(georg)''' | '''(georg)''' | ||
| Line 9: | Line 9: | ||
Here is a quick hack on re:dash, from the longitudinal table (a 1% sample of our clients): | Here is a quick hack on re:dash, from the longitudinal table (a 1% sample of our clients): | ||
https://sql.telemetry.mozilla.org/queries/1472/source | https://sql.telemetry.mozilla.org/queries/1472/source | ||
'''(ckprice)''' | |||
>https://sql.telemetry.mozilla.org/queries/1472/source | |||
This is awesome. I've forked it and will play around a bit. Given this, I'm assuming we can make the following statement: | |||
`Based on a 1% sample size of our clients, there are currently 1,925 Firefox clients with the d3d9fallback@mozilla.org system add-on installed.` | |||
>what is the use-case here? | |||
(probably should have led with this) | |||
The most recent requests we've had for system add-ons is to fix things (e.g. flipping prefs[0]). In these cases, relman wants to ensure that the fix is being rolled out to everybody in a timely manner. | |||
The other 'type' of system add-on is more heavy 'feature' work (Hello (rip), Pocket). Metrics here may not be as timely, but a signal at the browser level of users with the add-on installed is good to have to compare against the feature-level metrics being collected. | |||
'''(chutten)''' | '''(chutten)''' | ||