QA/Meetings/20091012

= Attendees =

People Present (lines said) ---
 * jlaska (176)
 * wwoods (38)
 * Viking-Ice (26)
 * kparal (24)
 * Oxf13 (18)
 * gtirloni (4)
 * denise (3)
 * nirik (2)
 * iarlyy (2)
 * zodbot (2)
 * pknirsch (2)

Regrets:
 * Liam Li (lili)
 * He Rui (rhe)
 * David Pravec (dpravec)
 * Adam Williamson (adamw)

= Agenda =


 * Proposed meeting agenda
 * [FIXME meetbot summary]

Preview Meeting follow-up
QA/Meetings/20091005


 * jlaska to catch up with mmcgrath on delivery of autoqa hardware to PHX

hardware shipment in transit to PHX2 ... jlaska and mmcgrath will work the next steps as hardware comes online


 * jlaska - sync-up with clumens to identify any blocking issues from https://www.redhat.com/archives/fedora-test-list/2009-October/msg00073.html

3 bugs from the Test_Day:2009-10-01_Anaconda/Features/StorageFiltering landed on the F12Beta blocker list, as well as 2 from the Test_Day:2009-10-08_RAID.

Oxf13 expressed concerns that recent blocker bugs could have been found prior to the freeze. Jlaska noted that we booked the F12 Beta freeze with several install test runs, including Test Results:Fedora 12 PreBeta Install, Test Results:Fedora 12 Beta TC Install before the Freeze, followed by Test_Day:2009-10-01_Anaconda/Features/StorageFiltering and Test_Day:2009-10-08_RAID after the freeze.


 * poelcat to check in on beta blocker status of 510249

Appears like this has been resolved

F-12-Beta RC1 QA strategy
RC ISO images are available and posted to http://alt.fedoraproject.org/pub/alt/stage/. However, we still have 1 unresolved anaconda bug on the blocker list (see ). Denise informed the group that Dave Lehman was investigating this issue and should have an update this afternoon.

Jlaska noted that Liam and Rui have already started executing to plan for tests that are not specific to the release candidate ISO media (see Test_Results:Fedora_12_Beta_RC1_Install). Once we have confirmation on the final ISO media kit, Liam will announce to fedora-test-list and invite testers to contribute feedback into the wiki.

AutoQA update
Wwoods spent some time last week focusing on the preupgrade F-12-Beta blocking bug (see ).

Focusing on a clean solution to provide a link to the autotest results on the autoqa-results emails and israwhidebroken.com front-end (see https://fedorahosted.org/autoqa/ticket/65).

Wwoods also looking into posting critical path package list to the wiki - currently blocked since JSON doesn't allow edit/create pages. Jlaska provided a link to something mmcgrath shared a while back (see http://git.fedorahosted.org/git/?p=fedora-data.git). Wwoods noted this handles uploading to the trac instance, not mediawiki.

Jlaska noted he might need guidance from wwoods when it comes to how best to incorporate israwhidebroken.com into the product instance (from a package standpoint). Wwoods noted that the content should correspond to the infrastructure turbogears SOP - http://fedoraproject.org/wiki/TurboGears_Infrastructure_SOP.

Packagediff update
kparal has implemented a majority of the important rpm checks (see https://fedorahosted.org/autoqa/ticket/54#comment:2)

kparal taking project naming suggestions to replace the current packagediff name (candidates include: 'rpmguard', 'rpmjudge' or 'rpmblame')

Some discussion followed on how best to incorporate kparal's script into autoqa. Wwoods advised that the script should work by itself much like install.py and sanity.py do in current autoqa. From there, just create a wrapper script to handle the integration with autotest.

How_to_Debug_ wiki pages
Viking_Ice started a great discussion around how best to improve the current Category:Debugging content - https://www.redhat.com/archives/fedora-test-list/2009-October/msg00112.html

A proposed template exists for use as a guide for all future pages (see Template:How_to_debug)

Viking-Ice would like feedback on a naming convention for future pages. Candidates include: "How to debug ". or "component problems" or "bug info ". Viking-Ice noted that campbecg helped define the different pages as:

As a reporter, looking at the wiki, I would see a page called "Bug Info ComponentX" and expect a page relating to known bugs on componentx, a page called "ComponentX Problems" to be full of known issues related to using componentx, and "How to Debug ComponentX" at a howto about how to actually debug it"

Both gtirloni and jlaska confirmed and agreed that the How to debug <component scheme made the most sense and that changes could be made as needed, but felt there was enough information available to start fleshing out additional pages. Viking-Ice noted he would investigate markmc's Virtualization bug reporting page next.

Upcoming QA events

 * 2009-10-12 - F12 Beta go/no_go meeting (@ 18:00pm - rel-eng meeting)
 * 2009-10-13 - BugZappers/Meetings
 * 2009-10-14 - Beta Project Wide Release Readiness Meeting
 * 2009-10-15 - i18n Test Day

= Action items =


 * jlaska will investigate the 5 anaconda F12Beta issues to determine when the failures were introduced
 * jlaska to investigate packaging of israwhidebroken.com for production instance
 * jlaska to request autoqa-devel@ for autoqa development discussion and patch review

= IRC transcript =

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