From Fedora Project Wiki

< FWN‎ | Beats

(create fwn 233 qa beat)
(create fwn 288 draft)
 
(50 intermediate revisions by the same user not shown)
Line 3: Line 3:


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>.
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]]
Contributing Writer: [[User:Adamwill|Adam Williamson]]
Line 8: Line 10:
<references/>
<references/>


=== Proven testers ===
=== 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<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 ===
 
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/>
 
=== Release criteria updates ===


At the QA weekly meeting of 2010-06-28<ref>http://fedoraproject.org/wiki/QA/Meetings/20100628</ref>, [[User:Jdulaney|John Dulaney]] offered to work on combining the two proven testers pages (concerning joining the proven testers, and how to conduct testing) into a single page and provide a draft to the list for review. John subsequently submitted<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091746.html</ref> his draft<ref>http://fedoraproject.org/wiki/User:Jdulaney/Proven_Tester</ref>. [[User:maxamillion|Adam Miller]] liked it<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/091820.html</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>.


Meanwhile, [[User:Adamwill|Adam Williamson]] proposed<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091745.html</ref> activating the proven testers group before Bodhi was changed to activate the requirement for proven tester feedback, as a way to make sure the process worked smoothly and get in some 'practice'. The response was generally positive. The proposal was, however, overtaken by events. [[User:Lmacken|Luke Macken]] announced the next day<ref>http://lists.fedoraproject.org/pipermail/devel/2010-June/138008.html</ref> that a new version of Bodhi had been put in place which enabled the proven tester feedback requirement, so Adam quickly announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091781.html</ref> the activation of the proven testers group and asked members to start testing immediately.  
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>.


He also promised to start the ball rolling on the mentoring process, and sent out a proposal<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091793.html</ref> the next day for a rough plan for proven tester mentoring. He suggested existing proven testers take sponsorship requests, ask the applicants to read the appropriate instructions, and then confirm that they are familiar with enabling updates-testing and posting feedback on updates, before sponsoring them into the proven testers group. [[User:Jkeating|Jesse Keating]] suggested<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091794.html</ref> asking applicants in general to take the initiative and start reading instructions and providing feedback, and link to some of their feedback on their application ticket, so their membership could be quickly approved as soon as a mentor got around to looking at the ticket. Adam thought<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091800.html</ref> this was a good idea, but felt that in practice it should be possible to personally pick up every current mentor request very quickly, given the number of requests and the number of existing proven testers.
[[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>.


Bob Lightfoot wrote about his proven tester testing process<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/091815.html</ref>, in case it was of use to others, or anyone could suggest improvements for him. [[User:till|Till Maas]] suggested a simplication<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/091845.html</ref>.
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>.
 
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>.


<references/>
<references/>


=== AutoQA ===
=== Update policy changes ===


At the QA meeting, [[User:Wwoods|Will Woods]] reported that the AutoQA team was working on a helloworld test (a test test), which would exist to check that watchers and hooks - particularly the bodhi watcher and hook - work correctly. This is a prerequisite for the dependency check test, one of the major AutoQA priorities. [[User:Jskladan|Josef Skladanka]] said he had a test instance of the ResultsDB up and running on one of AutoQA's infrastructure machines, and had rewritten the initscripts and rpmlint tests to store their results in the database. He would continue to work on converting other tests. [[User:Kparal|Kamil Paral]] announced that he had patched autoqa to use autotest labels correctly, which allows us to configure the actual running of tests in several ways - ensuring they are run on particular machine configurations. He pointed to a mailing list post<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-June/000742.html</ref> with a more detailed explanation.
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>.
 
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.
 
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.


<references/>
<references/>


=== Triage metrics ===
=== Update candidate notification ===


At the Bugzappers weekly meeting of 2010-06-29<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-06-29/bugzappers.2010-06-29-15.03.log.html</ref>, [[User:Jraber|Jeff Raber]] updated his progress with triage metrics. He had created a wiki page<ref>http://fedoraproject.org/wiki/User_Talk:Jraber</ref> to track his goals and progress, and had discussed some modifications to python-bugzilla with [[User:Wwoods|Will Woods]]. The group discussed the specific metrics Jeff was targeting, and made a few adjustments.
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/>
<references/>


=== Request for old DeltaISOs ===
=== 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>.


Andre Robatino asked<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091775.html</ref> for anyone who had old DeltaISO files he had provided for various releases to seed the corresponding torrents so he could retrieve them, for the purpose of creating an archive of all previous DeltaISOs, making it easier to reconstruct particular test releases from the past whenever this might prove useful.
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/>
<references/>


=== VERIFIED Bugzilla status ===
=== QA group representation at FUDCon Pune ===


Aaron Farnes proposed an update<ref>http://fedorahosted.org/fedora-qa/ticket/91</ref> to the bug workflow wiki page<ref>https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#VERIFIED</ref> regarding the VERIFIED state. [[User:Jlaska|James Laska]] reviewed and approved his changes, which were also discussed at the weekly meeting. Aaron made it clear that triagers and reporters should manually set the status when they checked that a pending update would resolve an issue, leaving the Bodhi update system or the maintainer to close the bug.
[[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/>
<references/>

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

  1. ↑ http://fedoraproject.org/wiki/QA
  2. ↑ http://fedoraproject.org/wiki/QA/Join

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].

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization
  3. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-22_I18n_Desktop
  4. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT
  5. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-29_PowerManagement
  6. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing
  7. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse
  8. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day
  9. ↑ http://fedoraproject.org/wiki/QA/SOP_Test_Day_management
  10. ↑ http://fedoraproject.org/wiki/QA/Test_Days/Create

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].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102599.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102600.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102601.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102636.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103680.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103127.html
  7. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103678.html
  8. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103557.html
  9. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103588.html
  10. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103679.html

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.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102493.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102497.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102503.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102502.html
  5. ↑ http://fedorahosted.org/fesco/ticket/664
  6. ↑ http://fedorahosted.org/fesco/ticket/667
  7. ↑ http://fedorahosted.org/bodhi/ticket/642
  8. ↑ http://fedorahosted.org/fesco/ticket/667#comment:26
  9. ↑ http://fedoraproject.org/wiki/QA/Meetings/20111107

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].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102981.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102982.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102992.html

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.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102869.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103000.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103341.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103585.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103840.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/104043.html
  7. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103163.html

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. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103712.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103728.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103739.html
  4. ↑ http://fudcon.in/sessions/fedora-testing
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=261435"