(create qa beat for fwn 170) |
|||
| Line 44: | Line 44: | ||
=== New group members === | === New group members === | ||
Two new members sent introduction emails: Bashir Souid<ref> | Two new members sent introduction emails: Bashir Souid<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg01253.html</ref> and Gireesh Sreekantan<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg01259.html</ref>. | ||
<references/> | <references/> | ||
Revision as of 22:58, 5 April 2009
QualityAssurance
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
Test Days
This week's first Test Day[1] was on the Radeon driver for ATI video cards, which has seen substantial changes for Fedora 11. The turnout was again excellent and many useful bug reports were filed. The developer present was Dave Airlie, and Adam Williamson and James Laska were present for the QA team. The second Test Day[2] was on power management. There was a good turnout of dedicated Rawhide users, and the results were quite positive: most testers found everything worked and few major bugs were discovered.
Next week's Test Day[3] will be on the UEFI[4] support in Fedora 11. UEFI hardware is not yet widely available, so this Test Day is mostly only of interest to Red Hat QA staff with access to testing hardware.
Weekly meetings
The QA group weekly meeting[1] was held on 2009-04-01. The full log is available[2]James Laska and Adam Williamson reported no progress this week with the Semantic mediawiki extension.
James Laska reported that packaging work on the Semantic extension for Mediawiki was progressing, and one package had already passed review. He also noted that he had created a test Mediawiki instance with the extension enabled, but had not yet been able to do much testing. Adam Williamson confirmed that he also had not had time to do much testing.
Adam Williamson noted that the release notes should cover the known problem with generating live USB images from the Fedora 11 Beta live CD images using Fedora 10, caused by the older version of syslinux it contains. The group agreed to file a bug on this issue and add a note to the release notes, linking to the bug report.
Will Woods and Jesse Keating reported steady progress with autoqa work, and hope to have two hooks - post-repo-update and post-tree-compose - running by next week.
Will Woods brought up the new blog[3] started by Warren Togami to note major issues in Rawhide, and suggested the QA group should propose to work together with Warren on the project.
The Bugzappers group weekly meeting[4] was held on 2009-03-31. The full log is available[5]. The group agreed that too much time was being spent on discussing moving the meeting time and there were too many problems to declare a move, so they agreed to keep to the present time for now.
The group discussed whether the How to Triage page[6] should stay as a single page or be split up. No broad agreement was reached. Eventually they agreed to focus on finalizing the content before worrying too much about organization. Some revisions to the content of the page were agreed upon, and Christopher Beland made them.
The next QA weekly meeting will be held on 2009-04-08 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-04-07 at 1500 UTC in #fedora-meeting.
- ↑ http://fedoraproject.org/wiki/QA/Meetings
- ↑ http://www.happyassassin.net/extras/fedora-qa-20090401.log
- ↑ http://rawhidewatch.wordpress.com/
- ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
- ↑ http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-31
- ↑ https://fedoraproject.org/wiki/User:Beland/How_to_Triage
Anonymous test result reporting
Paul Frields reported[1] that the infrastucture team had set up a special namespace for future Test Day pages on the Wiki. This namespace allows anonymous editing, so testers will be able to report their results without having to sign up for a FAS account (and so sign the CLA), which some testers were not comfortable with having to do.
New group members
Two new members sent introduction emails: Bashir Souid[1] and Gireesh Sreekantan[2].