Ticket #89 (closed enhancement: fixed)
Improve tracking blocker review status
|Reported by:||jlaska||Owned by:||poelstra|
Several bugs were changed so they fell off the tracking lists for Fedora 13. For example...
- 505189 - Going back to repo UI screen and and modifying Installation Repo causes traceback
- 577803 - Adding repository requiring network fails if network is down
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.
- Document usage of bugzilla flags (suggested by jkeating) to track blocker requests. This likely involves creating a bot to police the tags?
- Hardening the current keyword-based mechanism.
Additional discussion points include:
- Document generating exception report and document action plan for CLOSED Blocker bugs that did not go through VERIFIED.
- 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.