(creat half-assed 172 qa beat) |
mNo edit summary |
||
| Line 31: | Line 31: | ||
The discussion about how long to wait before closing NEEDINFO bugs was resolved by a proposal from [[User:poelstra|John Poelstra]]: whether to close after 30 or 60 days will be left to the discretion of individual triagers, while if there is in future any co-ordinated team working to resolve stale NEEDINFO issues not handled by the initial triager, they will use the 60 day method. | The discussion about how long to wait before closing NEEDINFO bugs was resolved by a proposal from [[User:poelstra|John Poelstra]]: whether to close after 30 or 60 days will be left to the discretion of individual triagers, while if there is in future any co-ordinated team working to resolve stale NEEDINFO issues not handled by the initial triager, they will use the 60 day method. | ||
The next QA weekly meeting will be held on 2009-04-22 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-04-21 at 1500 UTC in #fedora-meeting. | |||
<references/> | <references/> | ||
Revision as of 03:03, 20 April 2009
QualityAssurance
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
Test Days
This week saw two Test Days. The first[1] was a follow-up on the Fedora 11 rewrite of Anaconda's storage device code[2]. The second[3] was on the Presto plugin for yum, which enables the use of deltarpms for updates. The Anaconda test day verified that many issues from the earlier test day had been resolved and turned up several new bugs, many of which have been fixed already. The Presto test day was surprisingly uneventful: there was good participation but few bugs were discovered, the system worked well and reliably for almost every test.
Next week's Test Day[4] will be on the minimal platform feature[5], support for very small minimal installations. This is another test day which will require installation, so if you are interested in taking part, please make sure to have a spare system or partition on which you can install a Rawhide system. Of course, this week it only needs to be small!
- ↑ http://fedoraproject.org/wiki/Test_Day:AnacondaStorageRewrite_2009-04-14
- ↑ http://fedoraproject.org/wiki/Features/AnacondaStorageRewrite
- ↑ http://fedoraproject.org/wiki/Test_Day:Presto_2009-04-16
- ↑ https://fedoraproject.org/wiki/Test_Day:2009-04-21
- ↑ https://fedoraproject.org/wiki/Features/MinimalPlatform
Weekly meetings
The QA group weekly meeting[1] was held on 2009-04-15. The full log is available[2]. The group briefly discussed James Laska's plan to improve the customization possibilities for Test Day live CDs. James promised to send a mail to the list regarding his ideas here.
Adam Williamson reported that he had successfully had a post on the Rawhide nss / x86-64 issue added to the rawhidewatch blog[3], run by Warren Togami.
Adam Williamson reported on his progress in evaluating whether important bugs reported in the X driver Test Days are fully repesented on the Fedora 11 release blocker bugs list. The nouveau maintainer, Ben Skeggs, has already reviewed all nouveau bugs. Review of intel and radeon bugs in in process together with the regular triagers for these components, Matej Cepl and Francois Cami.
Will Woods provided an update on his progress in checking on PulseAudio's readiness for a Fedora 11 release. He noted that some significant problems remained in two ALSA drivers - snd-intel-hda and snd-intel8x0 - which cause problems in PulseAudio. These drivers are used by a very large amount of current sound hardware. However, patches to fix several problematic cases have been added to the Rawhide kernel recently, and the remaining problems can be worked around if fixes are not integrated prior to release time, so it should be possible to release Fedora 11 with a fairly reliable PulseAudio. The group discussed whether it would make sense to schedule a Test Day for Intel audio chipsets, but concluded it was too close to release time and the Test Day schedule was already too busy to make it practical.
The Bugzappers group weekly meeting[4] was held on 2009-04-14. The full log is available[5]. The meeting opened with a call for the Bugzappers group to be proactive in adding serious bugs to the Fedora 11 Blocker and Target bug lists. Several group members expressed the concern that they would not be able accurately to identify which bugs should be added to the list, so Adam Williamson and James Laska promised to discuss the issue at the next QA meeting and see if there was a way to provide firmer policies and guidance in future.
The group agreed to delegate the creation and organization of a Wiki area covering SOPs (Standard Operating Procedures) to John Poelstra.
The discussion about how long to wait before closing NEEDINFO bugs was resolved by a proposal from John Poelstra: whether to close after 30 or 60 days will be left to the discretion of individual triagers, while if there is in future any co-ordinated team working to resolve stale NEEDINFO issues not handled by the initial triager, they will use the 60 day method.
The next QA weekly meeting will be held on 2009-04-22 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-04-21 at 1500 UTC in #fedora-meeting.