Closed Bug 765010 Opened 12 years ago Closed 9 years ago

Produce a build adoption/desertion curve

Categories

(Mozilla Metrics :: Data/Backend Reports, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
Moved to JIRA

People

(Reporter: taras.mozilla, Assigned: joy)

References

Details

(Whiteboard: [JIRA STATMOD-21] [Telemetry])

In telemetry evolution, newer datapoints(builds within last 2 weeks) can not be trusted because they are still being adopted. We need to determine when a build tends to achieve critical mass, and when the usage drops off such that the numbers reported by that build will not change[significantly].

End result should enable us to put a vertical line in telemetry evolution saying "data left of this line is likely to not change much(ie build is at maximum number of users)" and another line for "numbers from builds right of this line are changing too much to be trusted".
Blocks: 765014
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Annie, I don't see any justification for resolving this bug. Was this closed by accident?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
i think we still want to work on this. We haven't quite determined what the scope of the analysis.
i don't think this was intentional.
Whiteboard: [Telemetry]
This is very similar to METRICS-995. See (2) in the comment. the current bug is about volatility whereas the metrics 995 is related to prediction.

This should be absorbed into Metrics-995 (maybe as a comment if Taras thinks this is different)

Regards
Saptarshi
https://metrics.mozilla.com/projects/browse/METRICS-995
Target Milestone: Unreviewed → Targeted - JIRA
Whiteboard: [Telemetry] → [JIRA STATMOD-21] [Telemetry]
Wontfixing, if this is still relevant, please re-open.
Status: REOPENED → RESOLVED
Closed: 12 years ago9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.