Compute churn / retention information for unique segments of Firefox
users acquired during a specific period of time.
script to be run daily that contructs the addon_aggregates table in re:dash
When the patches landed to dedupe crash pings (bug 1354468 has the list), did they work?
This is a one-off ETL job for getting separate hardware reports for users runing Windows 7 or Windows 10.
We don’t get a lot of call for addonHistograms anymore. Maybe we should ditch ‘em.
This notebook transforms pings from the SnoozeTabs testpilot test to a parquet dataset. Docs at https://github.com/bwinton/SnoozeTabs/blob/master/docs/metrics.md
Creates the JSON data files used by the Firefox Application Update Out Of Date dashboard.
How long does it take before we get crash pings from users that have pingSender vs users who don’t?