QA/Meetings/20100111

= Attendees =

People present (lines said)


 * kparal (129)
 * wwoods (47)
 * maxamillion (31)
 * jlaska (17)
 * cwickert (13)
 * lmacken (10)
 * Viking-Ice (9)
 * Oxf13 (7)
 * tk009_ (5)
 * nirik (4)
 * zodbot (3)

Regrets:


 * User:Liam
 * User:Rhe
 * User:jlaska

= Agenda =


 * Proposed meeting agenda
 * meetbot summary

Previous meeting follow-up

 * Viking-Ice investigating adding an LXDE test day to the F-13 test day schedule
 * maxamillion investigating scheduling a XFCE test day to F-13 test day schedule
 * adamw and rhe to discuss ways to add install testing as a QA activity
 * jlaska will reach out to mclasen for thoughts on F-13 fit'n'finish test days
 * Ideas posted to Talk:QA/Fedora_13_test_days. A main fit'n'finish track is likely not in plan for F-13.
 * jlaska to reach out ot fedora-{test,devel}-list for trading reviews
 * Request sent, see http://lists.fedoraproject.org/pipermail/devel/2010-January/043856.html
 * jlaska to reach out to beland for guidance/ideas on how to document the process (or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which place
 * No action taken yet

AutoQA project update
Discussion around the proposed QA changes for F-13 based on Fedora_12_QA_Retrospective. Begin identifying gaps and owners.

rpmguard package comparison

 * Milestone - https://fedorahosted.org/autoqa/milestone/Package%20update%20tests
 * Owner - User:kparal

Kamil informed the team that rpmguard has been merged into master. Also, Kamil posted an update to his blog about the changes included in the new version (see http://kparal.wordpress.com/2010/01/11/rpmguard-a-wiki-page-and-a-new-output-format/). Along with an improved output format, Kamil also documented each of the tests performed by rpmguard on the wiki (see https://fedorahosted.org/autoqa/wiki/rpmguard).

Kamil initiated discussion around designing a method for presenting package update test results (see https://fedorahosted.org/pipermail/autoqa-devel/2010-January/000110.html)

Deps/conflicts prevention

 * Milestone - https://fedorahosted.org/autoqa/milestone/autoqa%20depcheck
 * Owner - User:wwoods

User:wwoods informed the team that a new hook will be required (post-bodhi-update). This AutoQA hook will trigger when someone files a new update request in bodhi. Wwoods has been working with lmacken to figure out how to query for that info (and fix some bugs in the bodhi API).

install automation

 * Milestone - https://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan
 * Owner - User:lili, User:rhe

User:wwoods outlined the work needed to support integrating automated install tests into AutoQA by creatign a track milestone and several tickets to outline the eventual work required to integrate install automation into AutoQA.

User:lili and User:rhe have started exploring test design using the rats_install/install.py test as a starting point.

packaging/deployment

 * Milestone - https://fedorahosted.org/autoqa/milestone/Packaging%20and%20Review
 * Owner - User:jlaska

Current status on packaging:
 * autotest-client - undergoing review -
 * autoqa - packaged (see autoqa-0.3-2.fc12.src.rpm), will submit once autotest-client is accepted
 * gwt-* - investigating scope of packaging needed
 * autotest - packaged (see autotest-0.11.0-4.el5.src.rpm, will submit for review after gwt* accepted

Open discussion - 
= Upcoming QA events =


 * 2010-01-21 - Pre-Alpha Rawhide Acceptance Test Plan #1
 * 2010-01-28 - Pre-Alpha Rawhide Acceptance Test Plan #2
 * 2010-01-04 - Pre-Alpha Rawhide Acceptance Test Plan #3
 * 2010-02-05 - Alpha Blocker Meeting (F13Alpha) #1
 * 2010-02-11 - Test Alpha 'Test Compose' (boot media testing)
 * 2010-02-12 - Alpha Blocker Meeting (F13Alpha) #2

= Action items =


 * maxamillion bring back conversation about Xfce 4.8 updato on xfce@lists.fp.o and inform about conclusion
 * Viking-Ice write lxde tests and find a date for the test day
 * cwickert to file an infrastruture ticket for the lxde mailing list
 * adamw and rhe to discuss ways to add install testing as a QA activity
 * jlaska to reach out to beland for guidance/ideas on how to document the process (or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which place?

= IRC transcript =

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