QA/Meetings/20090715

= Attendees =


 * Adam Miller (maxamillion)
 * Adam Williamson (adamw)
 * David Pravec (dpravec)
 * Edward Kirk (tk009)
 * Kamil Paral (kparal)
 * Kevin Fenzi (nirik)
 * James Laska (jlaska)
 * Jesse Keating (f13)
 * Jóhann Guðmundsson (viking-ice)
 * John Poelstra (poelcat)
 * Will Woods (wwoods)

= Agenda =

Proposed meeting agenda

Previous meeting follow-up

 * [jlaska] - update fedora-qa privs so that viking_ice is on the default bcc
 * Updated fedora-qa trac instance ... viking_ice is now in the default bcc list.


 * [jlaska] - file a bunch of tickets to track wiki RFC's (requests for content) for debugging pages ... email list seeking volunteers after
 * http://tinyurl.com/n6n24f


 * [jlaska] - update QA/Goals wiki document
 * Spent some time on that this morning, but need to keep thinking about a good way to represent and allow for collaborative growth. I'm not ready to toss it out for review yet, but see transcript for link.

Fedora 12 Test Day schedule
A group of us gathered in fedora talk this week to hash out some ideas around QA milestones on the F12 schedule. A summary of the discussion was sent to fedora-test-list by poelstra.

Alpha Blocker Bug Day #1
Poelcat sent out a reminder about the first Alpha bug review meeting

What: F12Alpha Blocker bug meeting (https://bugzilla.redhat.com/show_bug.cgi?id=f12alpha) When: Friday, 2009-07-17 @ 17:00 UTC (1 PM EDT) Where: #fedora-bugzappers

[...] bugs in a single specific piece of hardware are not 'critical', only 'high' [...]
 * Adamw suggested looking at all F12blocker bugs and see if any are appropriate to block f12alpha too
 * Jlaska directed folks to the discussion around how to handle older F11Target bugs.
 * Poelcat updated the team on a draft SOP used to outline Blocker Bug meetings: User:Poelstra/blocker_bug_meeting_sop
 * Jlaska asked ... what type of issues constitute an Alpha blocker?
 * Adamw suggested using critical severity bugs in in critical path packages as release criteria
 * Mcepl indicated this approach might be too much ... which resulted in an update to the bug severity definition around

Maxamillion asked where the criteria for severity are established?
 * Wwoods provided current QA/ReleaseCriteria

Maxamillion asked where the bug severity definitions are?
 * Adamw linked to - BugZappers/How_to_Triage (section #9)
 * Adamw linked to - BugZappers/BugStatusWorkFlow detailed policy

Fedora 12 Test Day schedule
Schedule: https://fedoraproject.org/wiki/QA/Fedora_12_test_days Test Day candidates: Releases/12/FeatureList

Current list of wishlist events includes:
 * Revisit of X drivers (e.g. nouveau)
 * Anaconda F12 features
 * Storage cleanup
 * RAID
 * Partition UI cleanup
 * Upcoming NetworkManager changes
 * IPV6
 * System-wide connections
 * Mobile broadband updates
 * Audio test day

Others already scheduled include:
 * Virtualization
 * Dracut

AutoQA - update from wwoods
https://fedorahosted.org/autoqa

Completed all definition of all QA:Rawhide_Acceptance_Test_Plan test cases.

Two new test cases required some critical path work to be done first.
 * QA:Core_package_dependency_closure_test_case
 * QA:Core_package_existence_test_case

Two new additional basic functionality test cases:
 * QA:Network_basic_test_case
 * QA:Yum_simple_update_test_case

Plan for this week is to read up on autotest and begin automating test cases.

More info about the tasks / progress can be found here: https://fedorahosted.org/autoqa/milestone/israwhidebroken.com

Meeting time?
Dpravec cannot make the current meeting time and has requested considering a new day or time. Tk009 and Adamw suggested creating a meeting matrix page to coodinate times similar to that used in Bugzappers_meeting_matrix. Jlaska took this action item.

Updated F12 Schedule
f13 reminded the group about updates to the F12 schedule. This discussion was moved into the "news" portion of the agenda (see ).

Of test spins and trademarks
Viking_ice made the group aware of a discussion on fedora-advisory-board around trademark concerns

RHEL participants in Test Days?
Kparal asked how many RHEL people participate in Test Days.

Several people responded which can be summarized by: varies hugely by topic...some test days are essentially only _for_ that kind of person, but for something like, oh, nouveau test day, probably none.

= Upcoming QA events =


 * 2009-07-17 - Alpha Blocker Bug Meeting
 * 2009-07-21 - BugZappers/Triage_days
 * 2009-07-22 - 16:00 UTC - Next QA Meeting QA/Meetings/20090722

= Action items =


 * 1) [jlaska] - Notify team list (fedora-test-list) to solicit volunteers for help with Debugging pages (see http://tinyurl.com/n6n24f)
 * 2) [jlaska] - Create a QA:Meeting matrix similar to Bugzappers_meeting_matrix to determine best fit for meeting slots

= IRC Transcript =

Generated by irclog2html.py 2.7 by [mailto:marius@pov.lt Marius Gedminas] - find it at mg.pov.lt!