Regarding: https://product-details.mozilla.org/all.json + friends User case: - as an analyst, I want to know when a user Firefox is out of date, so I can use that several ways - as a covariate in analysis (for satisfaction, retention) - to inform the user it might be time to update (during SHIELD, about:support, etc.) To do so, I would some additional info: 1. When each version hits each channel. e.g. => when did 42.x go to AURORA. 2. More unusual builds (Yandex, Mozilla Online). 3. If possible, when did particular funnel cake build-ids go (for #growth, especially) (LESS IMPORTANT) Thanks! GL
(In reply to Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat ) from comment #0) > 1. When each version hits each channel. e.g. => when did 42.x go to AURORA. As your example mentions passed merge dates, I'd like to add that I am also very interested in future merge dates. As I see it now the only way to get that information is to use the Google Calendar API with authentication.
You need to log in before you can comment on or make changes to this bug.