Attendees

People present (lines said)

Unable to attend:

Agenda

Consult schedule for remaining QA tasks

Owner - AdamW, Hurry
Summary: Oct 01 - Hosted first F14Blocker review meeting last week - http://meetbot.fedoraproject.org/fedora-bugzappers/2010-10-01/f-14-blocker-review.2010-10-01-16.00.log.html; Oct 07 - Fedora 14 acceptance test run planned (see rel-eng ticket#4140 and results); Oct 08 - F14Blocker review meeting planned (see recap)
Next steps...: VERIFY ON_QA or MODIFIED F14Blocker bugs; Complete F14 pre-RC acceptance test (posting results and recap); Actively discuss bugs and testing on test@lists.fedoraproject.org
Upcoming milestones ...: Oct 14 - F14Blocker TC1 test run planned (see rel-eng ticket#4162 ); Oct 21 - F14Blocker RC1 test run planned (see rel-eng ticket#4166 ); Oct 26 - F-14 Go/No Go meeting (see Go_No_Go_Meeting)

Owner - jzeleny, jvcelak, rmeggins, omoris
Summary: Wiki page available - Test_Day:2010-10-14_OpenLDAP/NSS; Kparal notes the devel+qe folks are very active for this event
Next steps...: kparal will monitor whether custom test day live images are needed, and request help if needed; Announce event (test-announce@, planet, lwn etc...)

Owner - User:wwoods, User:kparal
Summary: wwoods will also add an rpm test transaction to depcheck to catch file conflicts -- moved to new ticket autoqa ticket#229; jskladan and wwoods investigating mash integration; kparal - we stopped checking updates-testing repos in the upgradepath test, because we're not sure how to do that properly - we need to consult FESCo (see fesco ticket#474 ); kparal started a thread about timing-sensitive tests - upgradepath and depcheck - how and when to correctly execute them; jskladan resultsdb patches for autoqa are waiting to be pushed to master; jskladan investigating a way for us to create generic testplan frontend
Next steps...: Monitor and discuss upgradepath topic during next FESCO meeting (see fesco ticket#474 ); Review resultsdb patchset for master; Wwoods integrating mash into depcheck test

Owner - AdamW
Summary: Adam sent a nice-to-have proposal to the list for feedback (see http://lists.fedoraproject.org/pipermail/test/2010-September/093833.html); It seems to be working out fine so far, we reviewed and accepted several NTH bugs at the blocker review meeting
Next steps...: Continue to monitor for feedback; Will activate the policy soon if no additional feedback