Hi, folks! So, we're nearing the final stretch of the severity / priority project. :) I have, as I noted previously, added some text to the triage guide to cover this: https://fedoraproject.org/wiki/BugZappers/How_to_Triage#Checklist_for_NEW_Bug_Triage (section 9) I have now added a section to the bug lifecycle page with a more complete and formal explanation, partly taken from the Beland 'Legend' draft page where we kicked around the competing systems: https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#Priority_and_Severity https://fedoraproject.org/wiki/User:Beland/Bugzilla_Legend#Severity_and_Priority I'll send an announcement to -devel-list soon. So, now, the priority / severity project is officially Open. BugZappers, please, if you haven't been already, start assigning a severity to all bugs as you triage them, according to the information above. This will be taken seriously and used in various ways. Talking about use, I will soon send out a review of bugs open on Rawhide and marked 'critical' severity. I'd like to have a review of this set of bugs each week. I don't necessarily want to be the one doing it, however. :) It'd be an ideal project for a community member: it's quite straightforward and requires no secret sauce, all you have to do is take a quick look at a saved query each week, do some copy/paste-ing, and pontificate. :) Let me know if you'd be interested in doing this. We'll also be reviewing all 'critical' bugs (and, if we get ambitious, even 'high' bugs in key components) during the blocker bug review meetings for F12, and the triage metric system will probably use the severity ratings for some metrics too. Thanks everyone who contributed on this project! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
