2009-05-27 - Fedora QA Meeting Recap

[James Laska]

Full IRC transcript available at
https://fedoraproject.org/wiki/QA/Meetings/20090527

= Attendees =

* Adam Williamson (adamw)
* Will Woods (wwoods)
* John Poelstra (poelcat)
* James Laska (jlaska)
* Jesse Keating (f13)

= Previous meeting follow-up =

Carry over from previous week:
# [adamw] - BugStatusWorkFlow - ask bugzilla guys to add a link from the
bugzilla fields description page to the wiki page, for fedora
#* working w/ dkl for other related bugzilla items, will leave on for
next week
# [jlaska] - Send informal test day feedback survey to fedora-test-list
and test day participants
#* fail :( - keeping on the list for next week where coordinated surveys
will go out
# [poelcat] - Check-in on F12 schedule updates
#* Added some granularity to the schedule
http://poelstra.fedorapeople.org/schedules/f-12/f-12-releng-tasks.html
#* Contemplating additional ideas
# [wwoods] - write a few more upgrade cases (encrypted root upgrade)
#* Created [[QA:Testcase_Anaconda_Upgrade_Encrypted_Root]] and updated
the Fedora 11 test results template
([[QA:Fedora_11_Install_Results_Template]]).

New items:
# [adamw] - clean up the [[Common_F11_bugs]] page to prime contributions
from others
#* cleaned up and stubbed out several Xorg related issues
# [adamw] - ping fedora docs team for possible collaboration around
common bug edits or translation
#* Spoke to docs team about how the common_f11_bugs page is being
handled, they were happy about it.  Did not get a definite on
translation of the page yet, will re-ping
# [jlaska] - contribute installer issues to Common_F11_bugs
# [fcami+adamw] - contribute X and KMS issues to Common_F11_bugs
# [adamw] - contribute alsa/pulseaudio issues to Common_F11_bugs
#* All above topics have representation in the [[Common_F11_bugs]] page.
adamw and jlaska suggested another sweep of the mailing list to add any
common issues.
#* adamw noted he was waiting to hear back from fcami for an updates
Radeon list

= Autoqa update =

* Project page - http://autoqa.fedorahosted.org
* Status - Revisit post F11

= F-11-GA Preparation =

* Blocker bugs (by component) - http://tinyurl.com/pqeq6n (currently
'''2''' OPEN issues remain)
* Schedule - http://fedoraproject.org/wiki/Releases/11/Schedule 
* Installation test results - [[QA:Fedora_11_RC_Install_Test_Results]]
* Release readiness meeting planned for today

Jlaska expressed an interest in reviewing where we are in the
schedule ... and discussion on any concerns around timing or next steps.

F13 pointed out that there are a ton of MODIFIED things that need to be
verified since we got a new kernel, anaconda, mkinitrd, rhpl,
policycoreutils.  Currently, there are 9 MODIFIED bugs on the F11Blocker
list (see http://tinyurl.com/pqeq6n).

Adamw pointed out that {{bz|502077}} was still in ASSIGNED, but has
positive test results from a koji scratch build that disables KMS for
the i865 VGA adapter.

Jlaska asked what expectations people have around testing the release
candidate images.  Having all MODIFIED bugs verified and a first pass at
testing of the RC media?  F13 indicated having both would be nice,
jlaska indicated that 1 to test and verify bugs was insufficient.  F13
pointed out that we may have  a few days based on the feedback for the
remaining kernel KMS bug.

Discussion followed around the exact nature and cause of {{bz|502077}}.
THe result was we need more test feedback against the koji-scratch
build.  Jlaska was going to get in contact with Jeff Bastian who has
matching hardware to help confirm the fix.

Wwoods indicated a new build of preupgrade would be pushed to stable
soon for F9, F10 and F11.

Jlaska expressed concern around only having 1 day in the schedule to
verify the 9 MODIFIED bugs and revalidate the media.  F13 suggested that
if all MODIFIED bugs turn out to be fixed (and introduce no
regressions), we are in good shape with the testing built up so far.
Jlaska suggested that testing would need to continue beyond the 1 day
for completeness, but the sync' process could start and the two could
work in parallel.  But there is risk should high severity non
workaround-able issues turn up.

= F-11 Common Bugs =

Update from [[User:adamwill]] on the F11 Common Bugs page.

* How to request common bug? - [[Common_F11_bugs#My_Bug_Is_Not_Listed]]

The meeting ran out of time to fully review this topic.  After the
formal meeting, the team discussed issues they felt needed
representation on the [[Common_F11_bugs]] list.  This included {{bz|
502077}} and {{bz|495323}}

= Open discussion =

== How to model RC1 test results wiki ==

Wwoods asked if the RC test results matrix would be cleared once the RC
lands.  Jlaska indicated he wasn't a big fan of clearing the page since
it loses history of previous results, but asked for ideas that could
retain history but clearly outline the newly tested items.  Some ideas
were:
* Just have a "Fedora 11 Final ... " results page
* Rename the current page to RC0, create a new RC1 page
* Clear out the WARN/FAIL results in the current page, await retesting

There wasn't a clear winner, the group indicated that having history was
important to potentially spot regressions.  Jlaska would likely pull
together a draft in the next day and send out to the list for review.

= Upcoming QA events =

* 2009-06-02 - [[BugZappers/Triage_days]]

= Next Meeting =

* 2009-06-03 16:00 UTC

= Action items =

* [wwoods] - create preupgrade test case and update test matrix
template 
* [jlaska] - create new RC1 test results page
* [adamw] - create common bug entry for {{bz|502077}}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-test-list/attachments/20090527/e7d8562e/attachment.sig>