Search results

...ting documentation on the wiki ([[QA/ReleaseCriteria)]] to assist triagers/QA in identifying and adding blockers to the Blocker List. This will be a collaborative effort with QA.

* [https://www.redhat.com/archives/fedora-test-list/2009-September/msg00444.html Proposed meeting agenda] = Upcoming QA events =

[https://www.redhat.com/archives/fedora-test-list/2009-July/msg00004.html Proposed meeting agenda] * [jlaska] - update [[QA/Goals]] wiki document

* jlaska+wwoods confirmed that things were on track for enabling automated test results sent to autoqa-results by F-11-GA ...e are known blocker bugs. Jlaska agreed, but noted it's difficult to plan QA time for testing the RC without specifics.

== How To Test == ...do for testing is OK, but it's much better to document what *I* can do to test your feature.

...'21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa]) == What to test? ==

* comphappy will email fedora-test-list with the link for the metrics beta and where to address bug reports. ...so far) * Should NEW triagers be asked to do NEEDINFO updates in 30 and 60 days if needed, or should this be left to triagers following the NEEDINFO chec

# Test the new desktop environment to ensure it works and integrates properly with == Test Plan ==

...yle="color: #488888" | f13, there hasn't been an updated anaconda in a few days. maybe worth pinging the anaconda team about first? ...07a40" | I dont' know if there have been that many commits in the last few days

* [https://www.redhat.com/archives/fedora-test-list/2009-November/msg00043.html Proposed meeting agenda] See [[QA/Meetings/20091026#Action_items]]

[https://www.redhat.com/archives/fedora-test-list/2009-June/msg00652.html Proposed meeting agenda] * [jlaska] - update [[QA/Goals]] wiki document

=== What to test? === The topic of this Fedora Test Day will be sharing of various things over the network. This includes files

| name = Upgrade Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

[https://www.redhat.com/archives/fedora-test-list/2009-August/msg00031.html Proposed meeting agenda] #* Sent ... see https://www.redhat.com/archives/fedora-test-list/2009-July/msg00655.html

[https://www.redhat.com/archives/fedora-test-list/2009-August/msg00242.html Proposed meeting agenda] == F-12-Alpha Test Compose ==

...e.net/fedora-qa #fedora-qa] ([http://webchat.freenode.net/?channels=fedora-qa webirc]) == What to test? ==

* [https://www.redhat.com/archives/fedora-test-list/2009-September/msg00307.html Proposed meeting agenda] = Upcoming QA events =

Follow-up from last meeting http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090311.log.html ** next steps to setup & configure a test instance and incorporate live data

* Continue discussion on #fedora-bugzappers and fedora-test-list@redhat.com | style="color: #854685" | anaconda is covered by Fedora QA, isn't it?

[https://www.redhat.com/archives/fedora-test-list/2009-July/msg00269.html Proposed meeting agenda] * [jlaska] - update fedora-qa privs so that viking_ice is on the default bcc