QA:SOP Blocker Bug Meeting
(Reword announcement sections)
m (Correct mailing list urls)
|Line 32:||Line 32:|
== Tear Down ==
== Tear Down ==
Send a summary of the meeting's findings and action items to /and /. As part of the email include information about the date and time of the next meeting.
Revision as of 18:45, 12 March 2010
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:
- 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=F26Blocker&hide_resolved=1
- Link to the apropriate Fedora Release Criteria (e.g. Alpha, Beta or Final) to guide decision making during the meeting
Use the following schedule to announce the event.
- One week before the meeting, send announcement to firstname.lastname@example.org
- A day before the meeting, send reminder to email@example.com and firstname.lastname@example.org
- The meeting leader should start the meeting and again link to the bug list s/he will be working from
- The group should agree on one person to update each bug appropriately in Bugzilla after it has been discussed (the 'bug updater')
- 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
- For 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
- After each bug has been discussed, the bug updater should update the bug report as appropriate, always including a note that the comments and/or changes are a result of the blocker bug meeting
- Identify a person to capture action and after-meeting follow-up items. Most of this can be captured in the individual bugs, but it is nice to send a post meeting summary back to the lists explaining what was accomplished at the meeting, for example, how many bugs were reviewed, and next actions the attendees plan to take. This is also an attractive way to advertise what happens at the meeting to draw more participants.
- FIXME--what is a clear way to explain how a group of people can efficiently review the bugs on the blocker list?
- FIXME--we need a wiki page that describes what kind of bugs belong on the <Release>Target tracker bug
Send a summary of the meeting's findings and action items to email@example.com and firstname.lastname@example.org. As part of the email include information about the date and time of the next meeting.