# Fedora Quality Assurance Meeting # Date: 2011-01-03 # Time: 16:00 UTC (11:00 EST, 17:00 CET) [1] # Location: #fedora-meeting on irc.freenode.net
Happy new year!
With the exception of several dedicated testers, things have been quiet over the last two weeks. I trust folks were able to enjoy some downtime and prepare for the new year and the upcoming release.
Let's kick off the first meeting of 2011 with a review of current activities. As always, topic suggestions encouraged!
= Proposed Agenda = 1. Previous meeting follow-up 2. Fedora 15 test days -- 7 slots remaining 3. Ticket#152 (fedora-qa) - TCMS requirements use cases / comparison 4. Ticket#154 (fedora-qa) - critpath test case development 5. AutoQA updates 6. <your topic here>
Thanks, James
[1] https://fedoraproject.org/wiki/Infrastructure/UTCHowto#How_can_I_convert_UTC...
Minutes and IRC transcript available at https://fedoraproject.org/wiki/QA/Meetings/20110103
= Attendees =
People present (lines said) * jlaska (127) * adamw (37) * Viking-Ice (23) * kparal (18) * rbergeron (4) * jskladan_home (3) * wwoods (2)
Unable to attend: * rhe (hopefully sleeping) * hongqing (hopefully sleeping)
= Agenda =
Proposed meeting agenda - http://lists.fedoraproject.org/pipermail/test/2011-January/096256.html MeetBot summary - http://meetbot.fedoraproject.org/fedora-meeting/2011-01-03/fedora-qa.2011-01...
== Previous meeting follow-up ==
* Bodhi feedback patch from fcami (see {{Ticket|infrastructure| 701}} awaiting review
No updates, still awaiting feedback https://fedorahosted.org/pipermail/bodhi/2010-December/000543.html
== Call for Test Days ==
Owner : adamw Summary * Call for ideas/owners for Fedora 15 [[QA/Test_Days]] Next steps ... 1. Schedule systemd event? 2. *HELP* - Approaching ''last call'' to pitch (or host) test days for Fedora 15. 3. Reach out to xorg-x11-drv maintainers to see if they want to move the test week at all
== Requirements review for Fedora test case management ==
Owner : rhe Summary * See http://fedorahosted.org/fedora-qa/ticket/152 -- Requirements review for Fedora test case management * Use case identification -- see https://fedoraproject.org/wiki/Rhe/tcms_use_cases * Use case comparison -- see https://fedoraproject.org/wiki/Rhe/tcms_Comparison Next steps ... 1. *HELP* - More feedback needed from testers (anyone who has participated or hosted an installation test event or test day)
== Critical Path test case development ==
Owner : Adamw Summary * See http://fedorahosted.org/fedora-qa/ticket/154 * * Updated links posted at http://lists.fedoraproject.org/pipermail/test/2010-December/096129.html Next steps ... 1. *HELP* - More feedback needed from testers and developers 2. If no additional feedback, and we assume no news is good news, the next step is converting existing test cases, and getting people started writing new ones developed 3. Reach out to f-e-k and bodhi teams to discuss tools integration
== AutoQA Update ==
Owner : Kparal Summary * Kparal pushed mkrizek's support for staging server into master Next steps ... 1. What's the status of depcheck? 2. Wwoods posting blog article explaining the need for {{Ticket| autoqa|248}} 3. Determine appropriate strategy for watcher and depcheck integration, and revise patchset as needed 4. Merge clumens branch into master
= Open discussion - <Your topic here> =
== Suggestions for improving IRC meetings ==
Owner - jlaska Summary * Jlaska asked for ideas/thoughts on improving IRC meetings * Suggestions included ... * Merge BugZappers and QA meetings * Post and solicit meeting topics on Friday, conditionally host meetings on Monday Next steps ... 1. Will post and solicit topics on Friday 2. No current action, but open to merging BugZapper and QA meetings in the future
= Action items =
- NA -