FWN/Beats/QualityAssurance: Difference between revisions

Latest revision as of 05:10, 17 November 2011

QualityAssurance

In this section, we cover the activities of the QA team^[1]. For more information on the work of the QA team and how you can get involved, see the Joining page^[2].

We apologize for the lack of a QA section for the last few issues of FWN: the QA team was very busy with Fedora 16 validation testing. This issue catches up with the QA team news from the last several weeks.

Contributing Writer: Adam Williamson

Test Days

In the past few weeks, we finished up the Fedora 16 Test Day schedule, with Graphics Test Week taking place at the start of September^[1] ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref>, virtualization test day taking place on 2011-09-15^[2], another i18n desktop test day on 2011-09-22^[3], an ABRT test day on 2011-09-26^[4], a power management test day on 2011-09-29^[5], printing test day on 2011-10-06^[6], Fedora packager plugin for Eclipse test day on 2011-10-13^[7], and Cloud SIG test day on 2011-10-20^[8]. Most of these test days passed off successfully with the work of the developers behind them, despite the QA team being very busy, so many thanks to those who organized and carried out these events, and those who turned up to do the testing.

The Fedora 17 Test Day cycle has not yet started. We welcome proposals for test days for the Fedora 17 cycle, and we usually accept all the proposals that are made. You can propose a test day for almost anything, and organize it yourself following the handy guide we provide^[9], or alternatively we can help out with the organization of the event. Information on how to propose a test day is available on the Wiki^[10].

Fedora 16 preparation

As mentioned above, Fedora 16 release validation took up almost all of the QA team's time during the last few months, with very challenging Beta and Final releases. There were a total of 12 candidate builds for Beta and Final combined, and the whole team put in tireless work running the set of validation tests against each build and then investigating and verifying the large number of blocker bugs identified. The team was able to contribute to the release eventually going ahead with only a one week slip to the Beta schedule and no slip of the Final schedule, a considerable achievement in the light of the many complex changes in the Fedora 16 feature list.

Release criteria updates

Largely as a result of the Fedora 16 validation process, there were several adjustments and additions to the release criteria in recent weeks. After discussion of the proposed kickstart / unattended installation release criterion concluded, Adam Williamson reported that he had committed his proposed modifications^[1]. He also committed a change to reflect the increased priority of EFI installations from Fedora 17 onwards^[2].

Adam also passed on a suggestion from Peter Jones to improve the clarity of the virtualization criteria^[3]. After an extensive discussion, an elegant wording suggestion from Albert Graham^[4] was eventually accepted and committed^[5].

Tim Flink raised the question to what extent support for Xen virtualization should be included in the release criteria^[6]. After a similarly enthusiastic discussion, it was eventually agreed that Xen DomU support - effectively, the ability to install successfully as a Xen guest - should be a Final release criterion^[7].

Adam also proposed downgrading some rarely-used kickstart deployment methods from Beta to Final in the criteria, requiring only the most commonly-used to be working at Beta stage^[8].

Finally, Adam proposed a criterion for i18n (translation) issues^[9]. After discussion, the proposal was agreed upon at a blocker review meeting later in the week^[10].

Update policy changes

In September, Karsten Hopp raised the issue of a security update for Fedora 14 which had been languishing in the updates-testing repository for some time^[1]. Adam Williamson explained that the amount of testers working on older releases was limited, and that the actual karma requirements for updates to be accepted were controlled by FESCo (the Fedora engineering steering committee), not the QA group^[2]. Chuck Anderson noted that he had the update in question installed, but was struggling for lack of information on how to test it properly^[3]. Rahul Sundaram suggested that Karsten file a ticket with FESCo to raise the issue^[4], and Karsten did^[5].

That ticket was merged with another similar one reported by Doug Ledford^[6], which became a topic of concern to FESCo. After several rounds of discussions, FESCo first decided to relax the requirements for critical path updates somewhat by allowing them to be sent through to the stable repository without the 'required' karma after a period of two weeks had elapsed^[7], and later proposed removing the requirement for critical path updates to receive positive karma from a proven tester^[8], effectively a proposal to end the proven tester system, as this is the only function it serves.

The QA group discussed this proposal at the weekly meeting of 2011-11-07^[9], agreeing that, while they had some reservations about the proposal, they were not definitely opposed to it, and recognized that critical path updates not receiving the currently-required karma is a significant problem.

Update candidate notification

Samuel Greenfeld asked if there was any system to notify testers of new candidate updates for specific packages, and to determine what packages are being actively used on a system^[1]. There were no takers for the second question, but for the first, Adam Williamson suggested using yum parameters that would allow one to specify only certain packages be pulled from the updates-testing repository^[2], and Till Maas pointed out that Bodhi can actually provide per-package RSS notifications^[3].

Proven tester meetings

As a response to the concerns about candidate updates not receiving enough karma, Kevin Fenzi ran a series of weekly proven tester meetups^[1] from 2011-09-21 to 2011-10-26. Recaps of these meetings are available in the mailing list archives^[2] ^[3] ^[4] ^[5] ^[6].

Kevin also proposed an updates-testing-info mailing list, containing only the mails about new packages in updates-testing^[7]. However, the consensus was against the idea, as it was felt that it was easy enough to simply filter the desired mails from the test mailing list for those who did not want to read the other traffic.

QA group representation at FUDCon Pune

Ankur Sinha asked whether anyone from the QA team would be present at the upcoming FUDCon in Pune, India and able to do a presentation on the group's activities^[1]. Adam Williamson replied that unfortunately none of the Red Hat team would be at the conference, but encouraged Ankur to take a shot at giving a presentation himself^[2]. A S Alam then stepped up to volunteer to lead a QA session^[3]. His session was scheduled for 2011-11-04^[4], but we have no report on the event - if you were present, please write to the mailing list and let us know how it went!

[1] ttp://fedoraproject.org/wiki/QA

[2] ttp://fedoraproject.org/wiki/QA/Join

[3] ttp://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau

[4] ttp://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization

[5] ttp://fedoraproject.org/wiki/Test_Day:2011-09-22_I18n_Desktop

[6] ttp://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT

[7] ttp://fedoraproject.org/wiki/Test_Day:2011-09-29_PowerManagement

[8] ttp://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing

[9] ttp://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse

[10] ttp://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day

[11] ttp://fedoraproject.org/wiki/QA/SOP_Test_Day_management

[12] ttp://fedoraproject.org/wiki/QA/Test_Days/Create

[13] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102599.html

[14] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102600.html

[15] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102601.html

[16] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102636.html

[17] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103680.html

[18] ttp://lists.fedoraproject.org/pipermail/test/2011-September/103127.html

[19] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103678.html

[20] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103557.html

[21] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103588.html

[22] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103679.html

[23] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102493.html

[24] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102497.html

[25] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102503.html

[26] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102502.html

[27] ttp://fedorahosted.org/fesco/ticket/664

[28] ttp://fedorahosted.org/fesco/ticket/667

[29] ttp://fedorahosted.org/bodhi/ticket/642

[30] ttp://fedorahosted.org/fesco/ticket/667#comment:26

[31] ttp://fedoraproject.org/wiki/QA/Meetings/20111107

[32] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102981.html

[33] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102982.html

[34] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102992.html

[35] ttp://lists.fedoraproject.org/pipermail/test/2011-September/102869.html

[36] ttp://lists.fedoraproject.org/pipermail/test/2011-September/103000.html

[37] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103341.html

[38] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103585.html

[39] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103840.html

[40] ttp://lists.fedoraproject.org/pipermail/test/2011-October/104043.html

[41] ttp://lists.fedoraproject.org/pipermail/test/2011-September/103163.html

[42] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103712.html

[43] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103728.html

[44] ttp://lists.fedoraproject.org/pipermail/test/2011-October/103739.html

[45] ttp://fudcon.in/sessions/fedora-testing

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[1]

[2]

[3]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[1]

[2]

[3]

[4]

@@ Line 2: / Line 2: @@
 == QualityAssurance ==
-In this section, we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>.
+In this section, we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>. For more information on the work of the QA team and how you can get involved, see the Joining page<ref>http://fedoraproject.org/wiki/QA/Join</ref>.
+We apologize for the lack of a QA section for the last few issues of FWN: the QA team was very busy with Fedora 16 validation testing. This issue catches up with the QA team news from the last several weeks.
 Contributing Writer: [[User:Adamwill|Adam Williamson]]
@@ Line 10: / Line 12: @@
 === Test Days ===
-Last week's Test Day was on the introduction of NFSv4 by default in Fedora 13<ref>http://fedoraproject.org/wiki/Features/NFSv4Default</ref>. The NFS maintainer, [[User:stevedSteve Dickson]], was kind enough to provide several automated test suites, and a good turnout of testers ran them on a variety of NFS configurations, providing valuable results.
+In the past few weeks, we finished up the Fedora 16 Test Day schedule, with Graphics Test Week taking place at the start of September<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref>, virtualization test day taking place on 2011-09-15<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization</ref>, another i18n desktop test day on 2011-09-22<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-22_I18n_Desktop</ref>, an ABRT test day on 2011-09-26<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT</ref>, a power management test day on 2011-09-29<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-29_PowerManagement</ref>, printing test day on 2011-10-06<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing</ref>, Fedora packager plugin for Eclipse test day on 2011-10-13<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse</ref>, and Cloud SIG test day on 2011-10-20<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day</ref>. Most of these test days passed off successfully with the work of the developers behind them, despite the QA team being very busy, so many thanks to those who organized and carried out these events, and those who turned up to do the testing.
+The Fedora 17 Test Day cycle has not yet started. We welcome proposals for test days for the Fedora 17 cycle, and we usually accept all the proposals that are made. You can propose a test day for almost anything, and organize it yourself following the handy guide we provide<ref>http://fedoraproject.org/wiki/QA/SOP_Test_Day_management</ref>, or alternatively we can help out with the organization of the event. Information on how to propose a test day is available on the Wiki<ref>http://fedoraproject.org/wiki/QA/Test_Days/Create</ref>.
+<references/>
+=== Fedora 16 preparation ===
-No Test Day is currently planned for this week. If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>http://fedorahosted.org/fedora-qa/</ref>.
+As mentioned above, Fedora 16 release validation took up almost all of the QA team's time during the last few months, with very challenging Beta and Final releases. There were a total of 12 candidate builds for Beta and Final combined, and the whole team put in tireless work running the set of validation tests against each build and then investigating and verifying the large number of blocker bugs identified. The team was able to contribute to the release eventually going ahead with only a one week slip to the Beta schedule and no slip of the Final schedule, a considerable achievement in the light of the many complex changes in the Fedora 16 feature list.
 <references/>
-=== Weekly meetings ===
+=== Release criteria updates ===
-The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2010-02-01. The full logs are available<ref>http://fedoraproject.org/wiki/QA/Meetings/20100201</ref>. [[User:Jlaska|James Laska]] reported that [[User:Beland|Christopher Beland]] had added links to the Bugzilla common_bugs queries to the Fedora 13 common bugs page<ref>http://fedoraproject.org/wiki/Common_F13_bugs</ref>.
+Largely as a result of the Fedora 16 validation process, there were several adjustments and additions to the release criteria in recent weeks. After discussion of the proposed kickstart / unattended installation release criterion concluded, [[User:Adamwill|Adam Williamson]] reported that he had committed his proposed modifications<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102599.html</ref>. He also committed a change to reflect the increased priority of EFI installations from Fedora 17 onwards<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102600.html</ref>.
-[[User:Kevin|Kevin Fenzi]] promised to look at updating the QA IRC bot, zodbot, to monitor the Fedora 13 blocker bugs instead of the Fedora 12 ones.
+Adam also passed on a suggestion from [[User:Pjones|Peter Jones]] to improve the clarity of the virtualization criteria<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102601.html</ref>. After an extensive discussion, an elegant wording suggestion from Albert Graham<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102636.html</ref> was eventually accepted and committed<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103680.html</ref>.
-[[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] reported that they had not yet discussed design ideas for the proposed AutoQA results database. Kamil felt that more people should be involved as the project would become important to several groups, if implemented. [[User:Jlaska|James Laska]] suggested a micro-FAD<ref>http://fedoraproject.org/wiki/FAD</ref>. Kamil mentioned that [[User:Lmacken|Luke Macken]] had suggested looking at his Kobo project<ref>http://fedorahosted.org/kobo/</ref> for inspiration. [[User:jkeating|Jesse Keating]] felt it might be over-engineered for the purposes of AutoQA. Will and Kamil agreed to organize a meeting during the week to begin designing the system.
+[[User:Tflink|Tim Flink]] raised the question to what extent support for Xen virtualization should be included in the release criteria<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103127.html</ref>. After a similarly enthusiastic discussion, it was eventually agreed that Xen DomU support - effectively, the ability to install successfully as a Xen guest - should be a Final release criterion<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103678.html</ref>.
-[[User:Adamwill|Adam Williamson]] reported that he had moved the privilege escalation policy discussion to the development mailing list<ref>http://lists.fedoraproject.org/pipermail/devel/2010-January/129978.html</ref>, and would go through the same feedback/revision cycle there as he had on the test list before finally escalating the draft policy to FESco.
+Adam also proposed downgrading some rarely-used kickstart deployment methods from Beta to Final in the criteria, requiring only the most commonly-used to be working at Beta stage<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103557.html</ref>.
-[[User:Adamwill|Adam Williamson]] reported on his and [[User:Rhe|Rui He's]] progres with documenting installation testing as a QA group activity. They had finalized the draft installation validation testing page<ref>http://fedoraproject.org/wiki/QA:Installation_validation_testing</ref> and created a draft desktop validation testing page<ref>http://fedoraproject.org/wiki/QA:Desktop_validation_testing</ref>. They had added a paragraph to the Join page<ref>http://fedoraproject.org/wiki/QA/Join#Release_validation</ref> which briefly explains the testing and link to the two more detailed pages. [[User:Jlaska|James Laska]] asked if the QA schedule should be altered to refer to 'release validation' rather than 'installation validation', to leave room for non-installation testing, and Adam said he thought this would be a good idea.
+Finally, Adam proposed a criterion for i18n (translation) issues<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103588.html</ref>. After discussion, the proposal was agreed upon at a blocker review meeting later in the week<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103679.html</ref>.
-[[User:Jlaska|James Laska]] reported that another rawhide acceptance testing event had come around during the previous week. This involves the creation and automated testing of a tree complete with installer. This time the acceptance test suite passed, but the installed system was unbootable due to a bug preventing the creation of the initramfs<ref>http://bugzilla.redhat.com/show_bug.cgi?id=559597</ref>. [[User:jkeating|Jesse Keating]] pointed out that this meant the installer was ready for 'last known good' status, but not the package set, and further asked whether the 'last known good' idea is intended to refer only to the installer or also to an associated package tree. There was general agreement that the 'last known good' page should list the tested installer and package tree, and note that the good installer may work with different package trees but could not be guaranteed to. James and [[User:Adamwill|Adam Williamson]] agreed to work on the 'last known good' Wiki page with information provided by Jesse.
+<references/>
-[[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] provided an AutoQA update. Will had created a working prototype of the dependency checking test, based on yum, which was 147 lines of code and took around 20 seconds to run. [[User:Jlaska|James Laska]] mentioned that he was hoping to see the rpmfluff tool for generating fake test packages become an official Fedora package soon. Kamil went over some updates to rpmguard; he had made it notice when two packages it is asked to compare are identical, and compare a package only to the previous package from stable or updates (not updates-testing).
+=== Update policy changes ===
-[[User:Jlaska|James Laska]] reported that [[User:Liam|Liam Li]] had added a dvd_install.py script to the autoqa repo<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-January/000178.html</ref>. He encouraged others to follow up with their thoughts on the script.
+In September, [[User:Karsten|Karsten Hopp]] raised the issue of a security update for Fedora 14 which had been languishing in the updates-testing repository for some time<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102493.html</ref>. [[User:Adamwill|Adam Williamson]] explained that the amount of testers working on older releases was limited, and that the actual karma requirements for updates to be accepted were controlled by FESCo (the Fedora engineering steering committee), not the QA group<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102497.html</ref>. [[User:Cra|Chuck Anderson]] noted that he had the update in question installed, but was struggling for lack of information on how to test it properly<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102503.html</ref>. [[User:Sundaram|Rahul Sundaram]] suggested that Karsten file a ticket with FESCo to raise the issue<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102502.html</ref>, and Karsten did<ref>http://fedorahosted.org/fesco/ticket/664</ref>.
-[[User:Jlaska|James Laska]] had continued working on the packaging plan for gwt<ref>http://fedoraproject.org/wiki/User:Jlaska/gwt#JPackage_Dependencies</ref> and hoped to be able to start packaging soon.
+That ticket was merged with another similar one reported by Doug Ledford<ref>http://fedorahosted.org/fesco/ticket/667</ref>, which became a topic of concern to FESCo. After several rounds of discussions, FESCo first decided to relax the requirements for critical path updates somewhat by allowing them to be sent through to the stable repository without the 'required' karma after a period of two weeks had elapsed<ref>http://fedorahosted.org/bodhi/ticket/642</ref>, and later proposed removing the requirement for critical path updates to receive positive karma from a proven tester<ref>http://fedorahosted.org/fesco/ticket/667#comment:26</ref>, effectively a proposal to end the proven tester system, as this is the only function it serves.
-[[User:Kparal|Kamil Paral]] mentioned that he was working on a package update acceptance test plan, and asked the group to provide any information they had on how other projects have approached this issue. [[User:Adamwill|Adam Williamson]] mentioned the Mandriva policies<ref>http://wiki.mandriva.com/en/Policies/SoftwareMedia</ref> <ref>http://wiki.mandriva.com/en/Policies/Support</ref> in the area, and suggested Kamil might talk to [[User:Vdanen|Vincent Danen]], who had managed the update process for Mandriva before joining Red Hat.
+The QA group discussed this proposal at the weekly meeting of 2011-11-07<ref>http://fedoraproject.org/wiki/QA/Meetings/20111107</ref>, agreeing that, while they had some reservations about the proposal, they were not definitely opposed to it, and recognized that critical path updates not receiving the currently-required karma is a significant problem.
-The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2010-02-02. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-02-02/fedora-meeting.2010-02-02-15.20.log.html</ref>. [[User:Adamwill|Adam Williamson]] admitted he had done nothing on the subject of bugs filed against orphaned packages.
+<references/>
-[[User:Rudchenkos|Sergey Rudchenko]] told the group about a script he had written to clean up abrt backtraces, providing bug 558883<ref>http://bugzilla.redhat.com/show_bug.cgi?id=558883</ref> as an example. He was interested in extending the script to compute the similarity of any two given backtraces, and also store multiple backtraces offline for comparison. [[User:Adamwill|Adam Williamson]] and [[User:Mcepl|Matej Cepl]] suggested he talk to the abrt team about integrating his ideas into abrt itself.
+=== Update candidate notification ===
-The next QA weekly meeting will be held on 2010-02-08 at 1600 UTC in #fedora-meeting. The next Bugzappers weekly meeting will be held on 2010-02-09 at 1500 UTC in #fedora-meeting.
+Samuel Greenfeld asked if there was any system to notify testers of new candidate updates for specific packages, and to determine what packages are being actively used on a system<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102981.html</ref>. There were no takers for the second question, but for the first, [[User:Adamwill|Adam Williamson]] suggested using yum parameters that would allow one to specify only certain packages be pulled from the updates-testing repository<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102982.html</ref>, and [[User:till|Till Maas]] pointed out that Bodhi can actually provide per-package RSS notifications<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102992.html</ref>.
 <references/>
-=== Nouveau 3D acceleration testing ===
+=== Proven tester meetings ===
+As a response to the concerns about candidate updates not receiving enough karma, [[User:Kevin|Kevin Fenzi]] ran a series of weekly proven tester meetups<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102869.html</ref> from 2011-09-21 to 2011-10-26. Recaps of these meetings are available in the mailing list archives<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103000.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103341.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103585.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103840.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/104043.html</ref>.
-[[User:Bruno|Bruno Wolff]] noted<ref>http://lists.fedoraproject.org/pipermail/test/2010-February/088305.html</ref> that experimental 3D acceleration for nouveau was now available in the mesa-dri-drivers-experimental package, and asked whether it was yet at a point where the developers would be interested in bug reports. [[User:Adamwill|Adam Williamson]] promised to pass the question along to the nouveau maintainer.
+Kevin also proposed an updates-testing-info mailing list, containing only the mails about new packages in updates-testing<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103163.html</ref>. However, the consensus was against the idea, as it was felt that it was easy enough to simply filter the desired mails from the test mailing list for those who did not want to read the other traffic.
 <references/>
-=== Fedora 13 Alpha blocker bug review meeting ===
+=== QA group representation at FUDCon Pune ===
-[[User:Adamwill|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-February/088321.html</ref> and later recapped<ref>http://lists.fedoraproject.org/pipermail/test/2010-February/088334.html</ref> the first blocker bug review meeting for Fedora 13. The summary of the meeting is available from meetbot<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2010-02-05/alphablocker1.2010-02-05-16.05.html</ref>. All current alpha blocker bugs were reviewed at the meeting.
+[[User:Ankursinha|Ankur Sinha]] asked whether anyone from the QA team would be present at the upcoming FUDCon in Pune, India and able to do a presentation on the group's activities<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103712.html</ref>. [[User:Adamwill|Adam Williamson]] replied that unfortunately none of the Red Hat team would be at the conference, but encouraged Ankur to take a shot at giving a presentation himself<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103728.html</ref>. A S Alam then stepped up to volunteer to lead a QA session<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103739.html</ref>. His session was scheduled for 2011-11-04<ref>http://fudcon.in/sessions/fedora-testing</ref>, but we have no report on the event - if you were present, please write to the mailing list and let us know how it went!
 <references/>

Search