From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 19:28, 22 March 2009 by Adamwill (talk | contribs) (create beat for fwn 168)

QualityAssurance

In this section, we cover the activities of the QA team[1].

Contributing Writer: Adam Williamson

Test Days

This week we had two test days, far more exciting than the boring regular one! The first[1] was on DeviceKit[2], which will replace HAL for disk and power management in Fedora 11. Turnout was not the highest, but those who came along were able to find several issues which are being addressed with the help of some of the developers involved, including David Zeuthen and Matthias Clasen. The second test day[3] was on Xfce[4], which is being updated to a major new release (4.6) in Fedora 11. A group of enthusiastic Xfce users showed up and were able to do some productive testing and refining of the Xfce environment together with the lead packager for Fedora, Kevin Fenzi.

Next week's test day[5] will be on Nouveau[6], the new default video driver for NVIDIA cards for Fedora 11. This is a very important event, as NVIDIA graphics cards are the most popular type, and the new driver is a fairly big change, so we need testing on a wide range of hardware to make sure it's ready. A live CD will be available for the day so you'll be able to test without a Rawhide installation. It will be held on Thursday (2009-03-26) in the #fedora-qa channel on Freenode IRC. If you have an NVIDIA graphics card, please make sure to come along, or - if you can't make it on the day - do the tests and fill out your results on the page another day.

Weekly meetings

The QA group weekly meeting[1] was held on 2009-03-18. The full log is available[2]. James Laska reported good progress in his work on the Semantic test result reporting extension for mediawiki. Packaging is complete and he is next planning to put up a test instance of mediawiki with the plugin enabled.

Adam Williamson reported that the Intel graphics adapter test day had been a success, and a follow-up event was in the works. He also reported that a Radeon test day had not yet been planned and promised to follow that up with the appropriate developers.

Jesse Keating was asked to report on the status of the beta release. He said that current Rawhide and particularly Anaconda was still too unstable and said he expected the beta release would slip if he could not get a Rawhide tree with a good Anaconda soon. He requested further testing of Rawhide installation from the QA group, and some help from the main QA group and the Bugzappers group on organizing and checking existing bug reports against Anaconda.

Adam Williamson reported that the Xfce test day was fully planned, and Kevin Fenzi reported that he had successfully generated some live CD images for the test day. Adam asked if someone could make sure these images would be available for download.

The Bugzappers group weekly meeting[3] was held on 2009-03-17. The full log is available[4]. John Poelstra asked for feedback on the draft Standard Operating Procedure for new memberships which he had sent to the mailing list. The group generally approved of the draft. It was also agreed that the 'triagers' and 'fedorabugs' groups in FAS should be merged or linked, so that anyone who joined the triagers group automatically becomes a member of fedorabugs. Edward Kirk proposed not putting the SOP online and into operation until the appropriate changes have been made in FAS, and this was agreed. Christopher said he will send a draft of the new 'How to Triage' page to the mailing list for discussion in the coming week.

The group discussed Adam Williamson's draft front page for the Wiki area. Discussion centred on the links in the Tools and Procedures section. Adam explained that he expected further work on the Wiki to clean up and merge the pages linked to in that section, so the number of links would be smaller. Christopher Beland fixed the links in the draft which were broken. Christopher proposed putting up the new page immediately and then working to clean up the pages further down the hierarchy, and this was agreed by the group.

The group discussed the revised Components and Triagers[5] wiki page and agreed the new layout was good. John Poelstra did not like the static statistics. Adam Williamson pointed out that it is planned to replace them with dynamically updated data from Brennan Ashton's metrics tool once it is complete.

John Poelstra brought up the potential meeting time and date change. Adam Williamson promised to send a mail to the mailing list summarising the results of the matrix survey to see if a definite conclusion could be made about whether to move the meeting.

The next QA weekly meeting will be held on 2009-03-25 at 1700 UTC (note changed time, in UTC reference frame) in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-03-18 at 1500 UTC in #fedora-meeting.

Wiki changes

Adam Williamson announced[1] that he had added a new column to the Components and Triagers[2] wiki page to make it easy to find out who is the maintainer of a given component (and other information on it). Christopher Beland changed[3] the stock response text for EOL bugs in an attempt to make it friendlier. Adam pointed out[4] that changes to the stock responses should be mirrored in the GreaseMonkey script. Chris also announced[5] a draft of a new How to Triage page for the group's feedback. Adam and Milos Jakubicek both approved of Chris' work and provided some suggestions to improve it.

Bugzilla status, priority and severity procedures

Christopher Beland began a discussion[1] about the use of various statuses, resolutions and the priority and severity fields in Bugzilla. Adam Williamson pointed out[2] that some of the more unconventional statuses and resolutions come from the RHEL side, where there is a specific and carefully defined workflow, and these statuses do not always mean exactly what they might appear to. Further to this, Tom Lane noted[3] that the Bugzilla page defining each status[4] contains accurate information on the RHEL workflow. He then suggested[5] that a similar page should be created to define a standard workflow for Fedora bugs, and included in Bugzilla. Jesse Keating suggested[6] that instead, the Fedora and RHEL workflows should be merged so that both would use the same statuses and resolutions in the same ways.