Revision as of 23:41, 14 July 2009

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. Important information to include is:
- Meeting time: 17:00 UTC (1 PM EDT)
- 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=446451&hide_resolved=1
- Link to the criteria used to determine a blocker bug <<FIXME>>
Announce the Blocker Bug Meeting to fedora-test-list@redhat.com and fedora-devel-list one week before the meeting.
Send a reminder email about the Blocker Bug Meeting to fedora-test-list@redhat.com and fedora-devel-list one day before the meeting.

@@ Line 4: / Line 4: @@
 * 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.
 == Setup ==