#90 Make blocker bug nag mails part of the SOP
Closed: Fixed None Opened 13 years ago by jlaska.

= problem =

We have a lot of bugs, and the deadlines for resolving bugs (where resolving == [fixing, documenting]) is not always clear.

= analysis =

During the lead up to F-13-RC, numerous reminder emails were sent to test@ and devel@ mailing lists noting the number and state of remaining blocker bugs. It is felt that, along with developer time of course, the attention to the blocker list contributed to the resolution of 67 blocker bugs from 2010-04-30 to 2010-05-06.

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

= enhancement recommendation =

  1. Recommend more frequent blocker status emails leading up to '''each''' major milestone. Unclear who should be responsible for sending these mails, QA, rel-eng or program mgmt?
  2. Update [https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting QA:SOP_Blocker_Bug_Meeting] with blocker meeting queries or ''python-bugzilla'' commands and where to send the mails (developers bcc'd?)

I've did the nagging for the Fedora 14 alpha and plan to start for the Beta today. I have not yet documented this process in the SOP, but plan to before the end of the release cycle.

Hey John ... I'm walking through the list of open F-14 QA tickets. It looks like the [https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Blocker SOP] was updated. Are there any updates you wanted to track here?

Yes this can be closed.

Login to comment on this ticket.

Metadata