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)
Release Engineering
Release Automation
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?
Comment 1•9 years ago
|
||
Bug 1334419 has some details on how we should test this kind of things.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•9 years ago
|
||
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 → ---
Reporter | ||
Updated•9 years ago
|
Updated•9 years ago
|
Priority: -- → P2
Comment 3•9 years ago
|
||
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%).
Updated•9 years ago
|
Component: Releases → Release Automation
Updated•7 years ago
|
Component: Release Automation: Other → Release Automation: Updates
Updated•2 years ago
|
Severity: normal → S3
Updated•10 months ago
|
QA Contact: rail
Updated•10 months ago
|
Component: Release Automation: Updates → Release Automation
You need to log in
before you can comment on or make changes to this bug.
Description
•