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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

 Several bugs were changed so they fell off the tracking lists for Fedora
 13.  For example...
  * [http://bugzilla.redhat.com/505189 505189  - Going back to repo UI
 screen and and modifying Installation Repo causes traceback]
  * [http://bugzilla.redhat.com/577803 577803  - Adding repository
 requiring network fails if network is down]

 = analysis =

 In F-13, a bugzilla keyword was used to denote blocker status. However,
 aside from reviewing bugzilla comments, there was no query-able method to
 determine whether a blocker request is open, approved or denied. This led
 to several Fedora 13 bugs that were 1) fixed in Rawhide, 2) Moved to
 MODIFIED or CLOSED and not included, but not included in Fedora 13 (e.g.
 RHBZ #505189 and RHBZ #577803).

 Not knowing which bugs were already reviewed, also introduced time wasted
 reviewing previously reviewed bugs during blocker review meetings.

 = enhancement recommendation =

 Recommend reviewing process changes to avoid the scenarios leading up to
 RHBZ #505189 and RHBZ #577803. Some options discussed so far include
  1. Document usage of bugzilla flags (suggested by jkeating) to track
 blocker requests. This likely involves creating a ''bot'' to police the
 tags?
  2. Hardening the current keyword-based mechanism.

 Additional discussion points include:
  1. Document generating exception report and document action plan for
 CLOSED Blocker bugs that did not go through VERIFIED.
  2. More frequent nag mails leading up to release milestones. Notification
 of NEW or ASSIGNED bugs goes to the maintainer, and MODIFIED bugs goes to
 QA.

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/89>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test


[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux