[Fedora QA] #89: Improve tracking blocker review status

[Fedora QA]

#89: Improve tracking blocker review status
--------------------------+-------------------------------------------------
  Reporter:  jlaska       |       Owner:  poelstra     
      Type:  enhancement  |      Status:  new          
  Priority:  major        |   Milestone:  Fedora 14    
 Component:  Wiki         |     Version:               
Resolution:               |    Keywords:  retrospective
--------------------------+-------------------------------------------------
Comment (by poelstra):

 1) We ran out of time and manpower to propose or implement the bugzilla
 flags that had been discussed on the list.  Given what we've seen so far
 in the Fedora 14 release cycle I'm not convinced that flags would speed
 our process up very much.  The greatest amount of time lag seems to be
 related to getting clear communication from the package maintainers as to
 where they are with fixing the bug.  Flags will not fix this problem.

 2) Blocker meetings appear to be running smoothly and we have started
 using the whiteboard keyword "AcceptedBlocker" when the people at the
 meeting determine that a bug has met the specified release criteria.  This
 process happens fairly quickly at the meetings.  I'm not convinced it
 would happen any faster if we waited for the responsible parties to set
 the flags outside of the meeting.

 3) I have an inquiry into the bugzilla team to see if there is a way to
 get an exception report of blocker bugs that have not transitioned through
 the VERIFIED state.

 4) We added a one week blocker bug nagging period before the Alpha, Beta,
 and Final change deadlines to the schedule.  It seemed to work okay for
 the Fedora 14 Alpha, but getting rapid maintainer response was difficult.

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/89#comment:1>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance