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 =
 * Proposed meeting agenda
 * MeetBot summary

Previous meeting follow-up

 * 1) adamw to check-in with wwoods on tooling needs for priv esc. test
 * 2) * Waiting for input from wwoods, will check-in again next week
 * 3) maxamillion seeking input from the Mentors group for guidance on mentor responsibilities
 * 4) * got 1 response so far, see below for continued discussion

Fedora 13 test status
Upcoming test milestones:
 * 2010-03-18 - Test Beta 'Test Compose'
 * Jkeating and dlehman working together to determine what packages to include in 'test compose' ... expected end of day today
 * 2010-03-25 - Test Beta 'Release Candidate'

Upcoming test days:
 * 2010-03-25 - Printing Test Day -- twaugh
 * 2010-03-30 - SSSD by default Test Day -- jlaska
 * 2010-04-01 - ABRT Test Day -- kparal

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 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:
 * we need a policy/sop for the 'proventesters' group
 * we need a guide to providing updates-testing feedback for branched + released explaining what should be tested and how to give feedback
 * 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
 * Improve documenting around using fedora-easy-karma

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.

= Upcoming QA events =


 * 2010-01-21 - Pre-Alpha Rawhide Acceptance Test Plan #1
 * 2010-01-28 - Pre-Alpha Rawhide Acceptance Test Plan #2
 * 2010-02-04 - Pre-Alpha Rawhide Acceptance Test Plan #3
 * 2010-02-04 - NFSv4 Test Day
 * 2010-02-05 - Alpha Blocker Meeting (F13Alpha) #1 (recap)
 * 2010-02-11 - Test Alpha 'Test Compose' (boot media testing)
 * 2010-02-12 - Alpha Blocker Meeting (F13Alpha) #2 (recap)
 * 2010-02-12 - Alpha Test Candidate verification (announcement)
 * 2010-02-18 - Alpha Release Candidate verification
 * 2010-02-18 - Color Management test day
 * 2010-02-19 - Alpha Blocker Meeting (F13Alpha) #3 (recap)
 * 2010-02-24 - Alpha Go/No-Go Meeting (20:00 EST)
 * 2010-02-25 - Yum Langpack plugin test day
 * 2010-03-10 - Pre-Beta Acceptance Test Plan #1
 * 2010-03-12 - Beta Blocker Meeting (F13Beta) #1 (recap)
 * 2010-03-18 - Gnome Disk Utility Storage Test Day
 * 2010-03-18 - Test Beta 'Test Compose' DELAYED
 * 2010-03-19 - Beta Blocker Meeting (F13Beta) #2 (recap)
 *  WE ARE HERE 
 * 2010-03-25 - Test Beta Candidate
 * 2010-03-25 - Printing Test Day
 * 2010-03-26 - Beta Blocker Meeting (F13Beta) #3
 * 2010-03-30 - SSSD by default Test Day
 * 2010-03-31 - Beta Go/No-Go Meeting (20:00 EST)
 * 2010-04-01 - ABRT Test Day

= 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

= IRC transcript =

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