QA/Meetings/20070503

= Fedora QA Meeting =

QA team membership
If you want to be counted as a member of the QA team, come down and say hi (or send me mail).

QA Beats
We need to determine "beats" - like the Docs Beats - for QA people to own. Some examples:
 * KDE
 * Firefox / Thunderbird
 * GNOME
 * Kernel
 * Installer
 * etc.

Bugzilla future plans
I'll have a proposal on the wiki about how we're going to use Bugzilla for F7 and beyond, and we'll go over that briefly.

Kernel bug triage
How can we keep the list of kernel bugs shorter and more manageable so davej and friends can get the important stuff fixed without dying of overwork?

QA Beats
List so far:
 * KDE
 * GNOME
 * XFCE
 * Firefox / Thunderbird
 * Kernel
 * Installer
 * Yum/Pup/Pirut
 * openoffice.org
 * Xorg

Bugzilla plans
Now through F7-release:

1. All Core + Extras bugs will be merged into the "Fedora Core" product 1. "Fedora Core" will be renamed to "Fedora" 1. At release time, all bugs filed against 'devel' will be put into 'NEEDINFO' 1. After 1 month, bugs still in NEEDINFO will be closed INSUFFICIENT_DATA

Post-F7:


 * We will create a f8-devel version for rawhide post-f7 release
 * We will also create versions for each f8 test release
 * There will be a new bugzilla frontend page on fedoraproject.org that only shows the 4 relevant versions:
 * FC6, F7, F8-devel, F8-testX (where X is the latest test release)

Kernel bug triage

 * We may create kernel subcomponents, e.g.: kernel/wireless, kernel/sata, etc.
 * Basic 'kernel' component will stick around
 * Bug triagers will move bugs to the right component
 * Would be nice if the components matched the  components
 * Further discussion with davej et. al will be needed before changes are made.