QA/Meetings/20091116

= Attendees =

People present (lines said)


 * jlaska (97)
 * adamw (70)
 * wwoods (41)
 * kparal (22)
 * lmacken (9)
 * Viking-Ice (7)
 * buggbot (3)
 * zodbot (3)
 * Oxf13 (1)

Regrets:
 * User:Liam
 * User:rhe

= Agenda =


 * Proposed meeting agenda
 * meetbot summary

Previous meeting follow-up

 * FTBFS topic?

Team agreed milos jacubicek's ftbfs proposal is tabled until he comes back with more info.


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


 * preupgrade test updates

Per last weeks FESCO meeting on preupgrade, QA team took an action item to update the preupgrade test cases (QA:Testcase Preupgrade and QA:Testcase Preupgrade from older release). Fedora QA trac ticket#30 is tracking this update. User:rhe and User:Kparal have adding their thoughts to the issue.

Fedora 12, almost there ...
Reviewing final QA tasks prior to release

F12Blocker

 * unresolved bug remains ... what's the plan?

Only remaining non-tracker bug is Can't Boot After F12 b2 DVD Upgrade on sytem with RAID1 /boot. Adamw suggested this isshue should be removed from the blocker list, as the team previously agreed it wasn't a blocker (it's actually not about RAID /boot but about drive order changing between install and upgrade).

Common_F12_Bugs
Jlaska asked the team to think about a method for dividing up remaining 22 common F12 bugs. Volunteers needed to help clear out the list of CommonBug? bugs needing notes.

Course of action is either ... DUD:
 * 1) Drop - Remove keyword CommonBugs
 * 2) Update - Already documented or addressed, add link to entry in bugzilla whiteboard
 * 3) Document - Document issue on Common_F12_bugs and add link to entry in bugzilla whiteboard

The current list:

There wasn't a lot of discussion in the meeting on volunteers or a strategy to help reduce the size of the list. Adamw noted he was confident in his ability to walk down the CommonBugs? list later today.

QA Retrospective
Let's hold a retrospective (e.g. post-mortem, release review etc...) next week. Please collect 1 or 2 ideas for things that when well, and the same for things that you'd like to see improved for Fedora 13. We will review and discuss during next weeks meeting.

jlaska will post email to the list after meeting to start discussion. Please feel free to respond with your input.

Over the next week, data will likely come back from Fedora 12 users for additional discussion items.

wwoods updates
A lot of time spent wrestling preupgrade last week. However, the current tasks include finalizing the post-koji-build with several patches kparal found and merging private autoqa branch work.

Held a discussion with Fedora release engineering group last week around a strategy for ensuring no broken dependencies are released. The solution will involve the post-koji-build, in addition to a post-bodhi-update hook. Also discussed writing a test that checks added/dropped/changed dependencies against known requirements in the public repo(s).

Lmacken and wwoods talked about how best to detect updated bodhi packages. Lmacken provided an update AMQP message/QMF events. Wwoods discussed the JFDI-design philosophy that's behind a lot of AutoQA at the moment.

16:46:46 wwoods: are there aspects of the koji watcher that kparal can assist with ... if it relates to rpmguard or package sanity? 16:46:58 time is running short so probably it'll be a discussion about design rather than a demo of a prototype 16:47:54 kparal's suggestion about having autoqa have a way to run tests locally is probably the best path forward 16:48:17 once that's written we can make sure rpmguard works as expected *in parallel* with setting up the watcher on the autotest host 16:48:43 perfect Plan for this week:
 * 1) Stop working on preupgrade
 * 2) add --local flag to autoqa
 * 3) polish rpmguard w/ kparal
 * 4) get watcher working
 * 5) test-enable rpmguard in production
 * 6) kparal suggested -- fix lots of issues we run into
 * 7) jlaska added -- success
 * 8) adamw asked -- profit?

kparal corrected the last sugguestion, with ... nope, world domination

kparal updates
Kparal updated the group on his AutoQA activities, which included several patches sent to autoqa-devel@lists.fedorahosted.org.

Kparal also identified several road blocks to participation and included several ideas for improving test development for newbies (see https://fedorahosted.org/pipermail/autoqa-devel/2009-November/000018.html). Out of that document jlaska has drafted an AutoQA Use Cases on the wiki: https://fedoraproject.org/wiki/AutoQA_Use_Cases. Kparal asked for suggestions and contributions to the document.

Kparal noted that the autoqa-devel list is being used more and more I would say, so if anyone is interested in autoqa development, please subscribe.

Kparal finished, but indicated he'll have more progress once the large autoqa-0.3 changes in wwoods private branch are merged into master.

lili and rhe updates
User:liam, User:rhe and User:mgracik held their first meeting on Friday, November 13 where they discussed the DRAFT proposal for adding installation verification to autoqa. The proposal is starting to take shape at Is_anaconda_broken_proposal.

Misc

 * Use cases - https://fedoraproject.org/wiki/AutoQA_Use_Cases
 * Packaging autotest - https://fedorahosted.org/autoqa/ticket/9
 * Packaging autoqa - https://fedorahosted.org/autoqa/ticket/3

Open discussion - 
= Upcoming QA events =


 * 2009-11-17 - Fedora 12 GA
 * 2009-11-23 - Fedora 12 QA Retrospective discussion

= Action items =


 * jlaska will propose Common_F12_Bugs after meeting for bug#530541
 * jlaska to send request for retrospective feedback to fedora-test-list@

= IRC Transcript =

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