So, sometime last year, we came up with the idea of doing a Bugzilla report
card as a way to measure each product's performance, track improvements, and
highlight the superstars.[1] Tonight I set out to start putting together a
rough overview of the type of information we'd like to include.
I'm thinking we'd want to do this as a quarterly or monthly thing with
evaluations sent out to Bugsquad(?) members quarterly or bi-yearly.
Here are a couple of examples that we might tweak. Nothing's set in stone, this
is just a very general sort of outline of the types of things we might include
in the report.:
Fremantle Browser:
UNCONFIRMED (moreinfo) 17 (8)
NEW (moreinfo) 57 (2)
REOPENED 2
ASSIGNED 4
RESOLVED (FIXED) (other) 114 (36) (78)
Total (DUPLICATE) 194 (31)
Resolution rate %58.7
(RESOLVED / Total)
"Positive" resolution rate %22.1
(Fixed / (Total - DUPLICATE)
Fremantle Hildon Application Manager:
UNCONFIRMED (moreinfo) 6 (3)
NEW (moreinfo) 26 (1)
REOPENED 0
ASSIGNED 0
RESOLVED (FIXED) (other) 54 (23) (31)
Total (DUPLICATE) 86 (16)
Resolution rate %62.8
(RESOLVED / Total)
"Positive" resolution rate %32.8
(Fixed / (Total - DUPLICATE)
Fremantle Modest:
UNCONFIRMED (moreinfo) 35 (17)
NEW (moreinfo) 70 (1)
REOPENED 10
ASSIGNED 3
RESOLVED (FIXED) (other) 148 (58) (90)
Total (DUPLICATE) 266 (60)
Resolution rate %55.6
(RESOLVED / Total)
Positive resolution rate %21.8
(Fixed / (Total - DUPLICATE)
[1]http://wiki.maemo.org/Task:Bugzilla_report_card
_______________________________________________
maemo-community mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-community
