QA/Meetings/20110207

= Attendees =

People present (lines said)
 * 1) jlaska (174)
 * 2) adamw (112)
 * 3) kparal (60)
 * 4) Viking-Ice (45)
 * 5) rbergeron (30)
 * 6) maxamillion (13)
 * 7) brunowolff (11)
 * 8) vhumpa (10)
 * 9) tflink (8)
 * 10) wwoods (2)
 * 11) robatino (2)
 * 12) Southern_Gentlem (1)
 * 13) CRCinAU (1)

Unable to attend:
 * 1) Rhe (hopefully sleeping)
 * 2) Hongqing (hopefully sleeping)

= Agenda =
 * Proposed meeting agenda
 * MeetBot summary

Previous meeting follow-up

 * 1) jlaska - update https://fedoraproject.org/wiki/Proven_tester#Mentoring_process with information about how to handle FAS group requests without a corresponding ticket
 * 2) * See change -- https://fedoraproject.org/w/index.php?title=Proven_tester&diff=219888&oldid=199131

AutoQA update - autoqa-0.4.4 and DevConf + FUDCon updates

 * Owner : kparal
 * Summary
 * jlaska created a great patch for autotest to automatically transfer all autoqa config files from the server to the client
 * wwoods improved his depcheck test and sent us final version proposal
 * jskladan posted final version of his new_koji_watcher code
 * kparal prepared a patch for upgradepath to work with the new post-bodhi-update-batch event (part of the new_koji_watcher stuff)
 * jskladan created new milestone in AutoQA trac - Finger Food - containing very small tasks suitable for AutoQA newbies -- https://fedorahosted.org/autoqa/milestone/Finger%20Food
 * kparal created new documentation AutoQA Development -- https://fedoraproject.org/wiki/AutoQA_Development
 * FUDCon:Tempe_2011 AutoQA slides available at https://fedoraproject.org/wiki/QA:Presentations


 * Next Steps ...
 * Complete packaging of compat-Django-1.0.4 security patches and submit for review (jlaska)
 * Wwoods to review current depcheck patch, and provide feedback
 * Continue testing and merging of new koji-watcher

Tue, Feb 08 - Alpha 'Test Compose'

 * Owner : rhe
 * Summary
 * See task#19 on Fedora 15 QA calendar (http://poelstra.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html)


 * Next Steps ...
 * 1) jlaska - ask rel-eng to file tickets for upcoming Alpha milestones
 * 2) jlaska - ping clumens about a new anaconda build for the alpha TC
 * 3) rhe or robatino - Announce ISO availability, and commence testing

Thu, Feb 10 Test Day -- FreeIPA v2

 * Owner : adamwill
 * Summary
 * See https://fedorahosted.org/fedora-qa/ticket/163
 * No updates in ticket or on wiki yet


 * Next Steps ...
 * 1) adamw - reach out to dmitri to check-in on FreeIPA test day prep

Fri, Feb 11 - Alpha Blocker Meeting (f15alpha) #3

 * Owner : jlaska
 * Summary
 * The 3rd scheduled blocker bug meeting will be hosted this Friday (see https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting).
 * The f15 Alpha blocker bug is https://bugzilla.redhat.com/show_bug.cgi?id=F15alpha. If you think a bug should block the release of F15 Alpha, set it as blocking that bug, and it will be reviewed at the meeting
 * The F15 Alpha nice-to-have bug is https://bugzilla.redhat.com/show_bug.cgi?id=f15alpha-accepted. This is for bugs which don't block the release but for which fixes should be allowed through alpha freeze.  You can propose bugs for it directly if you're sure they don't meet the blocker requirements; otherwise we usually put things on it when they don't get accepted as blockers


 * Next Steps ...
 * 1) jlaska - send F15Alpha blocker review announcement
 * 2) All - file bugs and propose as blockers

Testing Fedora 15 in KVM virtual machines

 * Owner : kparal
 * Summary
 * Kamil raised the topic on the mailing list -- see http://lists.fedoraproject.org/pipermail/test/2011-February/096856.html
 * After discussing the differences in environments, the team agreed that using KVM for testing is acceptable. However, testers and test organizers, should recognize that virt is only one of many environments that may need testing.
 * Additionally, the desktop validation matrix may need review to account for fallback mode, and other areas to ensure test coverage in multiple environments (bare-metal and virt)


 * Next Steps ...
 * 1) HELP - Adjustments to the desktop validation matrix (https://fedoraproject.org/wiki/QA:Desktop_validation_testing) may be required to accomodate for fallback mode, and/or other hardware environments.  Suggestions/drafts encouraged.

= Open discussion -  =

GNOME3 Test Day Summary

 * Owner : Adamwill
 * Summary
 * We had the first of three GNOME 3 test days on thursday, it went very well thanks to heroic work by the desktop team to get testing packages ready
 * We had several dozen testers and lots of juicy bugs reported.
 * Thanks to everyone who came and tested!!!
 * rbergeron asked about the process for how bugs are prioritized after the event, how do we know the bugs are prioritized and fixed as needed. Adamwill noted that he would review the bugs filed and recommend moving to the appropriate upstream (or downstream) blocker list.


 * Next steps ...
 * Adam expecting to send test summary later today

Best Practices for test day bug reporting

 * Owner : johannbg
 * Summary
 * After discussing the GNOME3 test day practice of filing functionality bugs upstream (bugzilla.gnome.org), and packaging bugs downstream (bugzilla.redhat.com), some debate ensued as to whether multiple bug reporting systems was an impediment to test day contributors.
 * One idea was to require that all future test days file bugs in the same downstream bugzilla
 * One idea was to add a caution/note to the test day SOP to noting that multiple bug trackers may be confusing to participants.
 * The meeting ran over the alloted time, and no agreement was reached


 * Next steps ...
 * johannbg agreed to continue discussion on test@lists.fedoraproject.org

HOWTO debug guide requirement

 * Owner : johannbg
 * Summary
 * johannbg suggested we should make it a requirement for test days to have how_to_debug pages ready present for the components that are being tested present and ready before the test
 * Adamwill noted that adding a suggestion to the test day SOP for a debug guide seems like a good idea


 * Next steps ...
 * Propose update to https://fedoraproject.org/wiki/QA/SOP_Test_Day_management

= Action items =


 * 1) jlaska - ask rel-eng to file tickets for upcoming Alpha milestones
 * 2) jlaska - ping clumens about a new anaconda build for the alpha TC
 * 3) adamw - reach out to dmitri to check-in on FreeIPA test day prep
 * 4) jlaska - send F15Alpha blocker review announcement
 * 5) Viking-Ice - solicit feedback on test@lists.fedoraproject.org to see whether we need to require only bugzilla.redhat.com use during test days

= IRC Transcript =

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