As always, IRC transcript and minutes available at https://fedoraproject.org/wiki/QA/Meetings/20100322
= Attendees =
People present (lines said)
* jlaska (123) * adamw (45) * maxamillion (32) * wwoods (19) * kparal (15) * jskladan (3) * zodbot (3) * Viking-Ice (3) * Southern_Gentlem (2)
Regrets: * [[User:liam]] * [[User:rhe]]
= Agenda = * [http://lists.fedoraproject.org/pipermail/test/2010-March/089489.html Proposed meeting agenda] * [http://meetbot.fedoraproject.org/fedora-meeting/2010-03-22/fedora-qa.2010-03... MeetBot summary]
== Previous meeting follow-up ==
1. adamw to check-in with wwoods on tooling needs for priv esc. test * Waiting for input from wwoods, will check-in again next week 2. maxamillion seeking input from the [[Mentors]] group for guidance on mentor responsibilities * got 1 response so far, see below for continued discussion
== Fedora 13 test status ==
Upcoming test milestones: 1. 2010-03-18 - Beta 'test compose' https://fedoraproject.org/wiki/Category:Fedora_13_Beta_TC_Test_Results * Jkeating and dlehman working together to determine what packages to include in 'test compose' ... expected end of day today 2. 2010-03-25 - Beta 'release candidate' https://fedoraproject.org/wiki/Category:Fedora_13_Beta_RC_Test_Results
Upcoming test days: 1. 2010-03-25 - Printing Test Day (twaugh) - https://fedoraproject.org/wiki/Test_Day:2010-03-25_Printing 2. 2010-03-30 - SSSD by default Test Day (sgallagh+jlaska) - https://fedoraproject.org/wiki/Test_Day:2010-03-30_SSSDByDefault 3. 2010-04-01 - ABRT Test Day (kparal+jmoskovc) - https://fedoraproject.org/wiki/Test_Day:2010-04-01_ABRT
Wwoods noted it would be great if there was an SOP available so that direct involvement with QA wasn't required. Jlaska pointed to https://fedoraproject.org/wiki/QA/SOP_Test_Day_management
== Updates Testing ==
There are some disparate efforts underway designed to improve the Updates testing workflow. Currently, the only defined process discusses using {{command|yum}} to enable ''updates-testing'' (see [[QA/Updates Testing]]). Jlaska asked the group for ideas on what tasks are needed to define a process by which testers can provide test feedback for updated packages.
Ideas included: 1. we need a policy/sop for the 'proventesters' group 2. we need a guide to providing updates-testing feedback for branched + released explaining what should be tested and how to give feedback 3. we need general guidance on that which applies to all packages; having specific instructions for some is also good, but the priority should be to define exactly what the acceptance testing is supposed to check 4. Improve documenting around using fedora-easy-karma
adamw and maxamillion took actions items for follow-up next week.
== Open discussion - <Your topic here> ==
=== Adjust meeting time? ===
* Kparal and jskladan asked whether the QA meeting time could adjust to keep the localtime the same, but change UTC. * This would moving the meeting from 16:00 UTC to 15:00 UTC during spring+summer. * No objections were made during the meeting, jlaska would raise the topic on the list as well.
= Action items =
1. wwoods and adamw to discuss tooling needs for priv esc. test 2. maxamillion will work on second draft of provenpackagers proposal 3. adamw will provide a draft for the update test plan 4. jlaska to post meeting time change request to test@l.fp.org