#221: Reduce Blocker Bug Review Meeting Length --------------------------+------------------------------------------------- Reporter: tflink | Owner: Type: enhancement | Status: new Priority: major | Milestone: Fedora 16 Component: Trac | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Comment (by adamwill): yeah, I had the same feeling going back and looking at it: it sure does have that 'wall of text' feeling. I'll take a look at breaking it down into bullet points. However, I'm not convinced the section discussed above belongs in the meeting SOP. The meeting SOP is supposed to be about _carrying out the meeting_, not about other tasks we might do to review blocker bugs. The blocker bug SOP just seems like the right place to put a task that's part of reviewing blocker bugs but is not part of the blocker bug review meetings, to me. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/221#comment:8> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test