Hi, I've been wondering how realistic the triaging is for setting a report priority.
I've worked in projects where it was popular to set a lot of tickets to "High" and "Medium", just to fail delivering about 80% of them in time, repeating this for a few development cycles, until giving up using this field in Bugzilla. Quick query[1] on any (open&closed, enh&bug) tickets in bugs.meego.com where the priority field has been changed to XX in the last YY days: Prio was set to> | Low |Medium| High | % Low in last 25 days | 34 | 217 | 172 | 8.03 in last 50 days | 96 | 549 | 334 | 9.81 in last 75 days | 116 | 734 | 493 | 8.63 in last 100 days | 177 | 1085 | 684 | 9.09 in last 200 days | 385 | 1994 | 1564 | 9.76 http://wiki.meego.com/Quality/Bugtriage_Guide#Priority states: * High --- SHOW STOPPER, must fix shortly in upcoming milestone and definitely for final product * Medium --- fix before product release, however for upcoming milestones, we can document the issue with possible work-around for visible defects Is the expectation of fixing ~90% of all incoming bug reports before "product release" (whatever that means) realistic, or are triagers doing something wrong by being optimistic? andre [1] URL: https://bugs.meego.com/buglist.cgi?priority=XXX&chfieldto=Now&chfield=priority&chfieldfrom=-XXd (replace XX respectively) -- Andre Klapper (maemo.org bugmaster) _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
