From Fedora Project Wiki

< FWN‎ | Beats

m (caps titles)
(correct link to qa log)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


This week's regular test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-12</ref> was on the Intel graphics card driver, particularly kernel mode setting<ref>http://fedoraproject.org/wiki/Features/IntelKMS</ref>. [[KristianHoegsberg|Kristian Høgsberg]] was the developer present. Several people showed up and provided valuable testing for the full set of test cases on various chips, giving a good overview of the current state of the driver in several situations. A follow-up event will be held before the release of Fedora 11 to check on the progress of fixes for the identified issues. Further testing in this area is still very helpful: the Wiki page contains full instructions on performing the range of tests, and the Results table is still available, so anyone with an Intel graphics adapter is encouraged to visit the Wiki page, perform the tests, and file bug reports as appropriate.
This week we had two test days, far more exciting than the boring regular one! The first<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-17</ref> was on DeviceKit<ref>http://fedoraproject.org/wiki/Features/DeviceKit</ref>, 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 [[User:Davidz|David Zeuthen]] and [[User:Mclasen|Matthias Clasen]]. The second test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-19</ref> was on Xfce<ref>http://fedoraproject.org/wiki/Xfce</ref>, 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, [[User:Kevin|Kevin Fenzi]].


Next week will be special, as two test days are scheduled. A special test day is planned for Tuesday<ref>https://fedoraproject.org/wiki/QA/Test_Days/2009-03-17</ref>, on DeviceKit<ref>https://fedoraproject.org/wiki/Features/DeviceKit</ref> - the partial HAL replacement scheduled to be included in Fedora 11. Anyone can help with this testing, so please come along and help out at the test day! The regular test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-19</ref> will be on the Xfce desktop environment<ref>https://fedoraproject.org/wiki/Xfce</ref>, particularly the new 4.6 release that will be part of Fedora 11. If Xfce is your desktop environment of choice, please come along and help make sure it'll be working properly in Fedora 11.
Next week's test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-26</ref> will be on Nouveau<ref>http://fedoraproject.org/wiki/Features/NouveauAsDefault</ref>, 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.
 
The DeviceKit test day will be held on Tuesday (2009-03-17) and the Xfce test day on Thursday (2009-03-19) in the #fedora-qa channel on Freenode IRC. Please come by to help make sure these features will be in shiny working order for Fedora 11!


<references/>
<references/>


=== Weekly Meetings ===
=== Weekly meetings ===
 
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-03-11. The full log is available<ref>http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090311.log.html</ref>. After a bracing discussion on how to send an apparently empty line to IRC, [[User:Jlaska|James Laska]] reported little progress in his work on making the Semantic test result reporting extension for mediawiki available as a package. He also deferred investigation of X.org test suites for next week. [[User:Adamwill|Adam Williamson]] noted that he had discussed one such suite, rendercheck, with [[User:bskeggs|Ben Skeggs]], and he will make a package available either as a scratch build or in the official repository to be used in the upcoming nouveau Test Day. The group agreed to see if it might be useful for other graphics test events.
 
[[User:jkeating|Jesse Keating]] and [[User:Wwoods|Will Woods]] reported that they had not had time to look at a method for identifying bugs caused by GCC 4.4 miscompilation issues. The group evaluated the response to the known bugs in this area, and decided that the responses suggested most issues would be resolved by fixes to GCC itself, and this should not cause major problems.


[[User:Adamwill|Adam Williamson]] reported that he and [[User:Fcami|François Cami]] had spoken to the intel and radeon driver developers about holding test days for those graphics drivers, and were in the process of organizing both events.
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-03-18. The full log is available<ref>http://www.happyassassin.net/extras/fedora-qa-20090318.log</ref>. [[User:Jlaska|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.


[[User:jkeating|Jesse Keating]] reported that a serious bug in squashfs in the Rawhide kernel was causing Rawhide installation to be impossible. This was to be fixed by a kernel update in the following day's Rawhide (which turned out indeed to be the case). He also reported that initial signing of packages for F11 was in progress in chunks, in order to ease the synchronization load for the mirroring system.
[[User:Adamwill|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 also reported that work on the substantial rewrite of Anaconda's storage code was in progress. The group agreed that this was quite close to the beta release, and that it seemed possible there could still be substantial problems in the code at the time the beta should be released, so discussed what kind of problems might be acceptable for a beta release and what might not. Despite some concern on the part of [[User:Wwoods|Will Woods]], the group agreed to evaluate issues on a case-by-case basis, taking care to make sure all issues in this area were added to the beta release blocker bug so they would be evaluated.
[[User:jkeating|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.


The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-03-10. The full log is available<ref>http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-10</ref>. [[User:Poelstra|John Poelstra]] reminded the group to evaluate all bugs with regard to the Fedora 11 blocker ('F11Blocker') and Fedora 11 target ('F11Target') blocker bugs. He also announced that Monday 2009-03-16 will be a bug blocker day, for the maintainers, QA and release engineering groups to go over the list of blocker bugs.
[[User:Adamwill|Adam Williamson]] reported that the Xfce test day was fully planned, and [[User:Kevin|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 group agreed to require a short self-introduction email to fedora-test-list as the criterion for becoming a member of the fedorabugs group in FAS. [[User:Tk009|Edward Kirk]] volunteered to write up this procedure into an SOP, as discussed at the previous meeting.
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-03-17. The full log is available<ref>http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-17</ref>. [[User:Poelstra|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. [[User:Tk009|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 again discussed the Wiki re-design, particularly how the front page should be laid out and how the main information flow should work from there. Everyone agreed that it was important to keep the front page short and simple and lay out a clear linear path for potential new members to follow. The group agreed to wait for [[User:Adamwill|Adam Williamson]] to finish his combination of [[User:Tk009|Edward Kirk's]] draft<ref>https://fedoraproject.org/wiki/User:Tk009/bugzappers</ref> and [[User:Beland|Christopher Beland's]] draft<ref>https://fedoraproject.org/wiki/User:Beland/BugZappers</ref>, with reference to the ideas discussed in the meeting. The group also discussed the new Tracking page (since re-arranged to become Components and Triagers <ref>https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref>), and agreed it was a good layout, but some of the content that had been merged into it should not have been. [[User:Adamwill|Adam Williamson]] suggested that the statistics be updated regularly and automatically via Brennan Ashton's metrics script.
The group discussed [[User:Adamwill|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. [[User:Beland|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.


[[User:Tk009|Edward Kirk]] reported that he had updated the bug workflow graphic<ref>http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow</ref> to reflect that NEEDINFO is no longer a status, but some members had trouble seeing the updated graphic due to caching issues.
The group discussed the revised Components and Triagers<ref>https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref> wiki page and agreed the new layout was good. [[User:Poelstra|John Poelstra]] did not like the static statistics. [[User:Adamwill|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.  
 
The group discussed the potential new meeting time with reference to the availability matrix<ref>https://fedoraproject.org/wiki/Bugzappers_meeting_matrix</ref>, but did not yet come to a decision.
 
The next QA weekly meeting will be held on 2009-03-18 at 1700 UTC (note changed time, in UTC reference frame) in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-03-11 at 1500 UTC in #fedora-meeting.
 
<references/>


=== Bugzappers Wiki Re-organization ===
[[User:Poelstra|John Poelstra]] brought up the potential meeting time and date change. [[User:Adamwill|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.


[[User:Beland|Christopher Beland]] worked hard to revise several areas of the Wiki, including a new Tracking page<ref>https://fedoraproject.org/wiki/BugZappers/Tracking</ref> which combined pages on active triagers, priority triage components, group goals and finding bugs<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00437.html</ref>. After feedback from [[User:Tk009|Edward Kirk]], [[User:Poelstra|John Poelstra]] and others, this was reduced simply to the Components and Triagers page<ref>https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref>, leaving the others separate for now. Christopher updated these pages also. [[User:Adamwill|Adam Williamson]] submitted his combined new front page draft for the group's review<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00662.html</ref>.
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.


<references/>
<references/>


=== Advertising Triage Days ===
=== Wiki changes ===


[[User:Beland|Christopher Beland]] pointed out that triage days are not advertised anywhere in the Wiki<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00695.html</ref>. [[User:Adamwill|Adam Williamson]] apologized and explained<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00713.html</ref> that this is because he is short on time at present as he is taking an internal Red Hat training course during his work days. He welcomed any help from the group in adding information about the triage day events to the Wiki.
[[User:Adamwill|Adam Williamson]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00885.html</ref> that he had added a new column to the Components and Triagers<ref>https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref> wiki page to make it easy to find out who is the maintainer of a given component (and other information on it). [[User:Beland|Christopher Beland]] changed<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00926.html</ref> the stock response text for EOL bugs in an attempt to make it friendlier. Adam pointed out<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00937.html</ref> that changes to the stock responses should be mirrored in the GreaseMonkey script. Chris also announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00931.html</ref> 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.


<references/>
<references/>


=== Metrics ===
=== Bugzilla status, priority and severity procedures ===


[[User:Beland|Christopher Beland]] reported<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00693.html</ref> that he could not access the pages for Brennan Ashton's triage metrics reporting system. Brennan thanked him for the feedback<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00727.html</ref> and explained that there was a hardware issue on the server. [[User:Poelstra|John Poelstra]] suggested<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00739.html</ref> that the code for the metric system be hosted in the Bugzappers group's git repository.
[[User:Beland|Christopher Beland]] began a discussion<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00942.html</ref> about the use of various statuses, resolutions and the priority and severity fields in Bugzilla. [[User:Adamwill|Adam Williamson]] pointed out<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00943.html</ref> 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, [[TomLane|Tom Lane]] noted<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00949.html</ref> that the Bugzilla page defining each status<ref>https://bugzilla.redhat.com/page.cgi?id=fields.html#status</ref> contains accurate information on the RHEL workflow. He then suggested<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00960.html</ref> that a similar page should be created to define a standard workflow for Fedora bugs, and included in Bugzilla. [[User:jkeating|Jesse Keating]] suggested<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00962.html</ref> that instead, the Fedora and RHEL workflows should be merged so that both would use the same statuses and resolutions in the same ways.


<references/>
<references/>

Revision as of 19:28, 22 March 2009

QualityAssurance

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

Contributing Writer: Adam Williamson

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

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.

  1. ↑ http://fedoraproject.org/wiki/QA/Test_Days/2009-03-17
  2. ↑ http://fedoraproject.org/wiki/Features/DeviceKit
  3. ↑ http://fedoraproject.org/wiki/QA/Test_Days/2009-03-19
  4. ↑ http://fedoraproject.org/wiki/Xfce
  5. ↑ http://fedoraproject.org/wiki/QA/Test_Days/2009-03-26
  6. ↑ http://fedoraproject.org/wiki/Features/NouveauAsDefault

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.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings
  2. ↑ http://www.happyassassin.net/extras/fedora-qa-20090318.log
  3. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
  4. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-17
  5. ↑ https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers

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.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00885.html
  2. ↑ https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
  3. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00926.html
  4. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00937.html
  5. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00931.html

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.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00942.html
  2. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00943.html
  3. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00949.html
  4. ↑ https://bugzilla.redhat.com/page.cgi?id=fields.html#status
  5. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00960.html
  6. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00962.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=91945"