Open Bug 1335732 Opened 9 years ago Updated 10 months ago

Detect when we have an abnormal number of users on an old version

Categories

(Release Engineering :: Release Automation, defect, P2)

Tracking

(Not tracked)

REOPENED

People

(Reporter: Sylvestre, Unassigned)

References

Details

In bug 1277925, we identified that we had a bunch of users stuck on an old beta version. As this was not on our radar for months, we should probably have a way to inform stakeholder that it is happening. Email notification, dashboard, etc?
Bug 1334419 has some details on how we should test this kind of things.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Following a private irc chat with Rail: I was more thinking about automation to say "we have an abnormal number users on the version XXX" Not about this specific technical issue. Maybe we should move that into telemetry or under some release management/engineer tooling
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
See Also: → 133573
See Also: 1335731335736
See Also: → 1337148
Priority: -- → P2
I've built this query to see the share of users per version and per channel: https://sql.telemetry.mozilla.org/queries/3238. We could write a simple script executed every day that warns us for weird percentages from that query (e.g. if a version, which is not the latest and not the latest - 1, is > 5%).
Component: Releases → Release Automation
Component: Release Automation: Other → Release Automation: Updates
Severity: normal → S3
QA Contact: rail
Component: Release Automation: Updates → Release Automation
You need to log in before you can comment on or make changes to this bug.