From aakashd: ---- The fixed blocker query seems to be wrong as its showed up 0 since we started using it. Looking into it further... This is probably the right query: https://bugzilla.mozilla.org/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=bug_status&chfieldfrom=-1d&chfieldvalue=resolved&field0-0-0=cf_blocking_fennec&type0-0-0=substring&value0-0-0=%2B&resolution=FIXED Mark, could you update the query for the FIXED blocker chart? ---- Also, the next FF beta is beta11, although currently no bugs are marked as such.
Created attachment 507124 [details] [diff] [review] Corrected mobile-fixed query; updated next beta to beta11 I wish there were a better way to update the next-beta, but since these are static HTML pages and there is no server component, there doesn't seem to be... we could do something complicated like looking at the cf_blocking_20 flags for betaX and taking the highest numerical version of X, but there's no guarantee that that's necessarily the next beta, if, for example, bugs are triaged into several upcoming betas... ah well.
Attachment #507124 - Flags: review?(ctalbert)
Pushed as http://hg.mozilla.org/automation/blocker-reports/rev/1071be9e8ff1 and deployed to brasstacks.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.