QA/Meetings/20091102

= Attendees =

People present (lines said)


 * adamw (72)
 * wwoods (32)
 * jlaska (15)
 * kparal (7)
 * Oxf13 (7)
 * tk009 (5)
 * zodbot (2)
 * buggbot (1)
 * thomasj (1)
 * Viking-Ice (1)
 * drago01 (1)
 * mchua (1)
 * seelchen (1)

Regrets:
 * User:Liam
 * User:rhe

= Agenda =


 * Proposed meeting agenda
 * meetbot summary

Previous meeting follow-up
See https://fedoraproject.org/wiki/QA/Meetings/20091026#Action_items


 * adamw will ask Milos to follow-up at next week's meeting or on the list on the FTBFS topic

Adam was in touch with Milos and asked for a follow-up on the FTBFS idea. So far no updates have been made. Milos asked when the next QA meeting would be, but doesn't seem to be available today.


 * Viking-Ice investigating creating a test case for bug#530452 ... and adding to F12 install matrix

No updates


 * wwoods to add roadmap/tickets for reworking shared autoqa code (watchers, test helper methods, etc) into a proper library

In progress. Will is working on a private git branch

Review beta test

 * open action items - http://meetbot.fedoraproject.org/fedora-bugzappers/2009-10-30/fedora-bugzappers.2009-10-30-15.01.html
 * mailing list feedback

James put this on to get a feel for how everyone thinks f12 beta testing is coming along with a view to whether we reckon we'll be ready to go RC on schedule. Adam asked the group for any particular thoughts/concerns.

TK009 asked how much time was left. Wednesday is the cutoff date (kparal directed the group towards the schedule). Adamw noted that ideally after Wednesday all the 'code bugs' should be fixed and further builds should only be addressing issues in the iso builds themselves.

Wwoods noted that after last Friday's EPIC blocker bug review (see recap), he felt there was a good handle on the scope of remaining issues.

With regards to blocker bugs, wwoods provided some data:

25 open bugs, none NEW, 12 ASSIGNED, 13 MODIFIED (see F12Blocker). Adam pointed out that 7, or 8, of the OPEN issues are still waiting for developer action. This includes some easy issues where the bug is waiting for tagging before being moved to MODIFIED. The group didn't think the remaining issues were cause for alarm. Wwoods and Adamw debated whether a community bug verification event was needed to help push through remaining MODIFIED bugs. Adam noted there were clear action items from the blocker review meeting. However, Adam reminded everyone that most of the bugs in MODIFIED need some sort of testing, so please take a minute to look through the MODIFIED items and provide any feedback you can, if you have time.

AutoQA update
Wwoods updated the team on his work to rebuild the autoqa code to provide a nice python library. For details see http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=lib/python;hb=wwoods-autotest. The hope is to have this code merged into master by the end of the week. Packaging and testing of a newer version of autotest-0.11 is underway as well (see ticket#9).

Kparal indicated there haven't been new developments with rpmguard this past week. Several new tickets arrived to track enhancements recommended on his blog. The main focus is integrating rpmquard into autoqa.

Open discussion - 
Some general discussion around the upcoming release candidate and the friday blocker bug day. Jlaska took an action item to catch up with denise and the installer team for any issues they were tracking for inclusion into the RC.

= Upcoming QA events =


 * 2009-11-02 - End of beta testing
 * 2009-11-04 - Compose release Candidate
 * 2009-11-04 - Test release candidate
 * 2009-11-06 - Blocker bug day

= Action items =


 * (carry over) - Viking-Ice investigating creating a test case for bug#530452 ... and adding to F12 install matrix
 * jlaska to check-in with anaconda-devel team for status on any issues they are monitoring for the wednesday RC compose

= IRC Transcript =

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