QA:SOP Blocker Bug Meeting
Blocker Bug Meeting SOP
- Most Fedora events should be self-hosting and capable of being led by non-subject matter experts. This SOP sets forth how to arrange and lead a Blocker Bug Meeting.
- Proactive review and handling of blocker bug lists is the one of the best ways to make sure our releases ship as closely on time as possible. During the Fedora 12 release cycle, several Blocker Bug Days are explicitly scheduled to make this a reality.
- Blocker Bug Meetings are not owned by any one team in Fedora. They are a collaborative effort between Release Engineering, Quality Assurance, Development, and Project Management.
Announce the Blocker Bug Meeting. Include the following important information in the announcement:
- Meeting time: 16:00 UTC (11:00 EST, 17:00 CET)
- Place: #fedora-bugzappers on irc.freenode.net
- Link to blocker bug to be reviewed (send tree display version). For example: https://bugzilla.redhat.com/showdependencytree.cgi?id=F25Blocker&hide_resolved=1
- Link to the apropriate Fedora Release Criteria (e.g. Alpha, Beta or Final) to guide decision making during the meeting
- Information to help participants convert UTI to their local time
- To convert UTC to your local time, take a look at
- or run:
- date -d '2010-03-19 16:00 UTC'
Use the following schedule to announce the event.
- One week before the meeting, send announcement to email@example.com
- A day before the meeting, send reminder to firstname.lastname@example.org and email@example.com
The meeting leader should start the meeting again link to
- The bug list s/he will be working from
- This page, reminder attendees the purpose and scope of the meeting
Next, proceed through the list of bugs. For each bug ...
- The meeting leader then sets the meeting topic to each bug on the list in turn (#topic bugurl)
- The group then agrees whether the bug is still accepted as a blocker; if not, whether it is downgraded to target or dropped from the list entirely. This decision should be based on the Release Criteria for the release in question
- The group then considers the status of work on fixing each blocker bug. It should be clear who currently has responsibility for each blocker bug and what the next required action is on each bug
- The meeting leader should summarize the discussion with a #agreed item before moving on to the next bug. If specific action beyond the immediate update of the bug report is needed, it should be noted with a #action item before moving on
- Lastly, identify someone who is responsible for updating the bug report as appropriate, always including a note that the comments and/or changes are a result of the blocker bug meeting
Finally, after the list of bugs has been reviewed, identify who is responsible for the #Tear_Down process. Typically, this is the meeting leader's responsibility, but it doesn't hurt to clearly identify who will be
Send a summary of the meeting's findings and action items to firstname.lastname@example.org and email@example.com. As part of the email include information about the date and time of the next meeting.