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

Fedora QA trac at fedorahosted.org
Thu Nov 25 00:51:42 UTC 2010

#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):

 Replying to [comment:1 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.

 Now that Fedora 14 is over I still think the process we ended up with by
 the end of the release worked well.  I still hold the opinion that ROI for
 the time and energy to implement flags just isn't there.

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

More information about the test mailing list