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

[Fedora QA]

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

 Using the script you linked to in bug#452399 ....
  1. http://fpaste.org/LF8Q/ -- Generate a list of bugs that depend on a
 given tracker (I used F14Blocker in my example)
  2. http://bit.ly/fEjczx -- Input that list of bugs into the query you
 provided (btw ... nice, I didn't think about the boolean NOT 'status'
 'changed to' filter).  I modified the query slightly to restrict the
 output to Resolution=ERRATA issues

 That yields 57 bugs.  Quick inspection of a few of those bugs shows that
 they indeed were not ever in VERIFIED state.  I'm completely fine with
 maintaining a shared bugzilla query that does #2 for us.  Periodically
 throughout the release, as new dependent Tracking bugs are added, we'll
 need to adjust the query in #2 to include the updated Tacking bugs.  That
 doesn't seem horrible.

 So the next question is ... now that we have a list of blocker bugs, fixed
 by bodhi updates, that weren't tested ... what can we do with that list.
 I'm inclined to say that the list should serve mainly as another data
 point during release.  We'll periodically monitor the list to make sure
 any scary issues are VERIFIED?  Any other ideas/thoughts?

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