Just about to uplift Bug 900694 to Beta (pre B1). We should fix existing badness, too.
6 years ago
Assignee: nobody → michael.l.comella
Flaggin' for trackin'. Release folks: this'll be the follow-on from Bug 900694 -- blowing away cached data to make sure we have an accurate snapshot of the user's add-ons, and are thus recording FHR events correctly.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 26
Comment on attachment 786979 [details] [diff] [review] Patch [Approval Request Comment] Bug caused by (feature/regressing bug #): Initial landing of FHR and the fix deployed in Bug 900694 (already uplifted to 24). User impact if declined: Misrecorded addon data will propagate until cache is invalidated (which occurs on version bump - this patch - or corruption) Testing completed (on m-c, etc.): Tested locally, on m-c one week, unit tests via github (https://github.com/mozilla-services/android-sync/pull/345) Risk to taking this patch (and alternatives if risky): Low risk - a version bump, whose behavior is tested by the unit tests linked above String or IDL/UUID changes made by this patch: None
Covered by unit tests
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in before you can comment on or make changes to this bug.