QA/Meetings/20100222

= Attendees =

People present (lines said)


 * adamw (101)
 * jlaska (98)
 * maxamillion (32)
 * kparal (28)
 * Oxf13 (28)
 * wwoods (10)
 * zodbot (4)
 * OldFart (4)
 * skvidal (2)
 * jskladan (1)
 * nirik (1)

Regrets:


 * User:liam
 * User:rhe

= Agenda =
 * Proposed meeting agenda
 * meetbot summary

Previous meeting follow-up

 * 1) adamw noted that the Privilege_escalation_policy is no longer a draft and has been reviewed by FESCO
 * 2) adamw thanked folks for joining last weeks Color Management test day (see recap).

Fedora 13 Alpha test status
Alpha Test Compose verification has completed. From the wiki pages, there were 26 bugs identified during testing.

Alpha RC#1 is available for testing. Instructions for downloading and providing feedback available at:
 * Test_Results:Fedora_13_Alpha_RC1_Install
 * Test_Results:Fedora_13_Alpha_RC1_Desktop

Current list of unresolved bugs blocking the Fedora_13_Alpha_Release_Criteria ...
 * NEW - Input devices don't work
 * NEW - Failed dependencies and login problem; basic video driver installation, F13 Alpha RC1.
 * NEW - Incorrect repourl during install
 * NEW - /etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/cobbler/webui_sessions(/.*)?  (system_u:object_r:httpd_cobbler_content_rw_t:s0 and system_u:object_r:public_content_rw_t:s0).
 * ASSIGNED - kernel 2.6.33 strips coredump when using pipe in core_pattern
 * ON_QA - GDM starts endlessly

The team discussed current Alpha test efforts, including the list of blocking bugs above. The severity of several bugs was discussed, and different workarounds were suggested for the SELinux issues.

Jkeating noted he was available to spin up any new composes on demand. New compose requests should go into the existing ticket (see ticket#3319).

The group concluded that the Alpha is at risk for the scheduled Go/No_go meeting on Wednesday.

development/13 bug procedures
Are there documentation updates needed for filing and closing development/13 bugs? Adamw noted this was on the agenda for tomorrows Bugzappers meeting.

Defining the QA team
A topic we may want to visit in the future ... define what it means to be on the QA team, and how to gain membership. With the current no frozen rawhide implementation, critical path package updates need someone from rel-eng and/or QA to validate the fixes prior to acceptance into the 'updates' repo. Maxamillion offered to send a first draft of what it means to be a QA team member.

Security Spin
Maxamillion looking for people to help draw up test cases for tools on the security spin. Created SecuritySpin:QA_Brainstorm wiki page to track ideas. To assist, please take a look at the email thread. Jlaska suggested pulling in the test day hosts (see Test_Day:2009-09-01_Sectool).

= 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
 *  WE ARE HERE 
 * 2010-02-24 - Alpha Go/No-Go Meeting (20:00 EST)
 * 2010-02-25 - Yum Langpack plugin test day

= Action items =


 * 1) maxamillion to draft up some proposed policy docs for qa FAS group membership
 * 2) jlaska / maxamillion to co-ordinate with sectool test day hosts tmraz, mbarabas and pvrabec who may be able to contribute

= IRC transcript =

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