QA/Meetings/20061220

= Fedora QA Meeting - December 21 2006, 0100 UTC, #fedora-testing on freenode =

Agenda
1. Review actions from last week 1. Review F7 plan - https://www.redhat.com/archives/fedora-advisory-board/2006-December/msg00170.html i. Do we have a plan/tools/docs for testing each feature listed? i. Can we test all that stuff in the time given? i. Divide the features into categories/tiers, e.g.: i. Required - release will slip until it works i. Desired - we want this to work but we may be forced to ship it with known bugs and fix them later i. Delicate - If this doesn't work by Feature Freeze (Test2), it can't go in at all i. Others? 1. Define general QA workflows - "walkthroughs" for things we test. i. How do we test new packages in updates-testing? i. What about new stuff in rawhide? i. How do you do installer testing? i. What do you do to test a new release (like Test1)? i. Get these things on the wiki or mailing list so we can discuss and improve them. 1. QA tool updates - fedora-updates-system (lmacken), RHTS (poelstra/dmalcolm), SNAKE (wwoods) i. fedora-updates-system (lmacken) i. RHTS (poelstra/dmalcolm) i. SNAKE (wwoods) 1. Anything else