[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

2009-08-10 - 16:00 UTC - Fedora QA meeting recap

Full IRC transcript available at

= Attendees =

* Adam Williamson (adamw)
* David Pravec (dpravec)
* Edward Kirk (tk009)
* James Laska (jlaska)
* Jesse Keating (f13)
* J├│hann Gu├░mundsson (viking-ice)
* John Poelstra (poelcat)
* Kamil Paral (kparal)
* Will Woods (wwoods)
* (Southern_Gentleman)
* Clyde Kunkel (oldfart)
* (yoyoned)

* Liam Li (lili)
* He Rui (rhe)

= Agenda =

[https://www.redhat.com/archives/fedora-test-list/2009-August/msg00242.html Proposed meeting agenda]

== Previous meeting follow-up ==

* No action items from previous meeting

== F-12-Alpha Test Compose ==

Thank you all for helping Liam gather information on the state of
F-12-Alpha installer.  Produced quite a few bugs, several of which
landed as Alpha blocker bugs.

[https://bugzilla.redhat.com/showdependencytree.cgi?id=507676&hide_resolved=1 F-12-Alpha blocker bug]
* [[QA:Fedora_12_Alpha_Install_Test_Results]]

There will likely be another request for testing from Liam once the
Alpha candidate has landed, so stay tuned.  

Jesse Keating noted it feels like the QA team is testing too late and
guaranteeing a schedule slip, but this could be due to the late delivery
of the test compose and other test blockers.

=== Open Issues ===
==== alt.fedoraproject.org download speeds ====
The infrastructure team is curious how download speeds held up during
the test compose
* No major issues reported
* Kparal experienced slow downloads, but the bottleneck appears to have
been a bandwidth limit on the Brno side ... not the fedoraproject side.

==== Rawhide still contains anaconda-12.7 ====
Jesse Keating indicated that no new anaconda builds were able to fully
complete an installation and the he was holding off from tagging a new
anaconda build for testing.

Dpravec shared his desire for a stable working anaconda each week.
Discussion that followed identified a possible difference in how
anaconda upstream development is absorbed into Fedora, when compared to
other upstream projects.

Adamw proposed an idea that ''anaconda packaging should be treated like
packaging 'any other upstream', and when we hit development freezes,
only necessary changes - not full unstable anaconda point upgrades -
should be committed''.  Continued discussion followed as to whether
Fedora asserts this claim to other upstream projects.

==== Verification of MODIFIED bugs ====

Once a new anaconda build is available, Jlaska asked for help from
testers to work down the list of MODIFIED bugs on the F12Alpha blocker
list (see

== F-12-Alpha Readiness ==

In preparation for 2009-08-12 - Release Readiness Meeting, I'd like to
poll the team for thoughts on high profile areas.

=== Open Issues ===

==== Installer readiness ====


==== Xorg-x11 readiness ====

Adamw informed the team that as of the time of the meeting,
xorg-x11-server and xorg-x11-drv-nouveau were tagged for rawhide and
known working.  There were no new unresolved Alpha blocking xorg related
failures on the radar.

==== General Feature readiness? ====
There are items on the [[Releases/12/FeatureList]] that appear to not be
resolved for the Alpha.  If the Alpha is intended to be feature
complete, why do we have features that are incomplete?

There appears to have been a misunderstanding on what the term ''feature
complete'' means.

Jkeating suggested we have QA owners tied to features responsible for
ensuring each feature has a test plan or is testable.  Jlaska expressed
concerns on whether that was the right solution.  Adamw pointed out that
this exercise was done for F-11, and met with ''a resounding chorus of

== In the news ==

=== Alpha Compose ===

Coming to a fedoraproject website near you ...

Once Alpha candidate is available, Fedora QA will be responsible for:
* Testing the alpha candidate -- stay tuned for information from Liam
regarding QA testing of the candidate
* Verifying MODIFIED Alpha blocker bugs -- 

Upcoming release events:
* 2009-07-29 - '''<span style="color:#ff0000">DELAYED</span>''' -
Alpha Test Compose]
* 2009-08-06 - '''<span style="color:#ff0000">MISSED</span>''' - Compose
Alpha Candidate 
* 2009-08-06 - '''<span style="color:#ff0000">MISSED</span>''' -
2009-08-13 - Test Alpha Candidate
* 2009-08-10 - Alpha go/no_go 
* 2009-08-13 - Sync to mirrors

=== Fit'n'Finish Peripheral Test day ===

This Tuesday, August 11, 2009 will be the 3rd fit'n'finish test day on
Peripherals.  Matthias Clasen
[https://www.redhat.com/archives/fedora-test-list/2009-August/msg00192.html announced on fedora-test-list] ...
  We are interesting in the problems you face when plugging anything 
  into your computer, be it a mouse, a keyboard an external hard 
  drive, a modem, a printer, a camera, a phone, a music player, a 
  GPS or whatever. 

=== NetworkManager Test day ===

This Thursday August 13, 2009 will be our first main track test day on
NetworkManager.  Candidate features for the test day include:

* [[Features/MoreNetworkManagerMobileBroadband]]
* [[Features/NetworkManagerIPv6]]
* [[Features/NetworkManagerSystemConnections]]

More details landing in [[Test_Day:2009-08-13_NetworkManager]], stay
tuned.  Adamw planned to flesh out some wiki content later in the day.

== Open discussion ==

=== AutoQA update from wwoods ===

Wwoods gave a quick update on recent developments on the AutoQA front.
The highlights include:
* Finalized the install test
* Major re-factoring of the current autoqa code base
* updated watcher scripts
* updated docs to reflect changes

=== <your topic here> ===

= Upcoming QA events =

* 2009-08-06 -
Alpha Candidate Compose]
* 2009-08-11 - [[BugZappers/Triage_days]]
* 2009-08-11 - [[Test_Day:2009-08-04_Fit_and_Finish:Peripherals|
Fit'n'Finish - Peripherals]]
* 2009-08-13 - [[Test_Day:2009-08-13_NetworkManager|NetworkManager]]
* 2009-08-17 - [[QA/Meetings/20090817]] at 16:00 UTC 

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]