From Fedora Project Wiki

< FWN‎ | Beats

m (caps titles)
(first draft of beat for 167)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


This week's regular test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-05</ref> was on the rewritten handling of storage devices in Anaconda<ref>http://fedoraproject.org/wiki/Features/AnacondaStorageRewrite</ref>. [[User:Dlehman|Dave Lehman]], [[User:Clumens|Chris Lumens]] and [[User:Jgranados|Joel Granados]] were the developers present. Several people showed up and provided valuable testing in a wide range of scenarios, and the developers were able to identify and resolve several bugs. Further testing in this area is still very helpful. The Wiki page contains instructions for using a supplementary image while installing Rawhide, to use the new storage code successfully, but the code will soon be available directly in Rawhide, so testing can be performed simply by attempting to install Rawhide in as many different storage scenarios as possible.
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.


Next week's test day<ref>http://fedoraproject.org/wiki/QA/Test_Days/2009-03-12</ref> is tentatively scheduled for testing Intel graphics devices, especially the new kernel mode setting support and identifying performance regressions from Fedora 10. It will be held on Thursday (2009-03-12) in the #fedora-qa channel on Freenode IRC. If you use an Intel graphics card, please come by to help make sure it will be well-supported in Fedora 11 - the more testing, the better the code!
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.
 
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-04. The full log is available<ref>http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090304.log.html</ref>. [[User:Wwoods|Will Woods]] pointed out that the next week's meeting would be an hour earlier for most people, after the onset of Daylight Savings Time. [[User:Adamwill|Adam Williamson]] and [[User:jkeating|Jesse Keating]], as the resident West Coast representatives, led a revolt against having to wake up at 7 a.m., and the group agreed to move the meetings to 1700UTC from 2009-03-11.
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:Jlaska|James Laska]] reported on the progress of the project to make the Semantic test result plugin for mediawiki available. He reported that he is currently trying to make the plugin work in his test setup prior to building a Fedora package for it, as the infrastructure group requires all software used for Fedora systems be available as a Fedora package. [[User:Adamwill|Adam Williamson]] offered to help with the packaging.
[[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:Wwoods|Will Woods]] and [[User:jkeating|Jesse Keating]] reported that there had been no progress on the autoqa systems this week, as Jesse had been tied up doing the mass rebuild of Rawhide.
[[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.


[[User:Wwoods|Will Woods]] reported that 33 of the Fedora 11 proposed features<ref>http://fedoraproject.org/wiki/Releases/11/FeatureList</ref> have not yet been reviewed by the QA group to ensure that they include a workable test plan, and appealed for help from the group in getting this process completed. He noted that features for which test days have already taken place are likely to have workable test plans in place, as these are generally necessary for a test day to happen, so suggested at least those features could be quickly reviewed and, most likely, approved.
[[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 test day for the new nouveau driver<ref>http://fedoraproject.org/wiki/Features/NouveauAsDefault</ref> for NVIDIA hardware was already planned and prepared, but that he was waiting on developer replies for the planned Intel KMS<ref>http://fedoraproject.org/wiki/Features/IntelKMS</ref> and automatic fonts and MIME installer<ref>http://fedoraproject.org/wiki/Features/AutoFontsAndMimeInstaller</ref> test days. [[User:Johannbg|Jóhann Guðmundsson]] suggested having a single big graphics test day, but [[User:Adamwill|Adam Williamson]] explained that he did not want to do that as it would be too large and unmanageable. [[User:Jlaska|James Laska]] suggested running the Piglit<ref>http://people.freedesktop.org/~nh/piglit/</ref> OpenGL test suite as part of the test days for drivers with usable 3D support (radeon and intel).
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]] reported that the mass rebuild of Rawhide was complete. [[User:Adamwill|Adam Williamson]] pointed out that three large bugs had resulted from GCC 4.4 optimization problems after the rebuild, and [[User:Wwoods|Will Woods]] reported that this had been discussed during the release engineering meeting. Will noted that the new hashing system in RPM was not backwards compatible, the upshot being that those upgrading from Fedora 11 Alpha to current Rawhide need to run 'yum update rpm' first. He queried why yum did not automatically update itself and rpm before other packages, and [[User:jkeating|Jesse Keating]] explained it was because this would usually bring in hundreds of other packages via Python and glibc dependencies in any case, and so was not worth the effort.
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:jkeating|Jesse Keating]] reported that live CD image builds from current Rawhide were not working very well, and Anaconda is often broken while its developers are busy working on the storage rewrite and EFI features.
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-03. The full log is available<ref>http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-03</ref>. The group agreed to make sure the two most important Greasemonkey scripts for triagers were easily available in a central place, and this was implemented by making them available directly from the Wiki Tools page<ref>https://fedoraproject.org/wiki/BugZappers/Tools</ref>.
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:Beland|Christopher Beland's]] plan to re-organize the Wiki area. It was agreed that a mailing list discussion should take place to create and agree upon a new front page for the Bugzappers wiki area, and work could then progress on re-writing and re-arranging other pages based on the organization system set up by the new front page. The group also discussed and agreed upon a plan for revising the Components page<ref>https://fedoraproject.org/wiki/BugZappers/Components</ref>, and [[User:Beland|Christopher Beland]] pointed out that the current bug flow diagram is incorrect, as it dates from before NEEDINFO was converted from a bug status into a flag. [[User:Tk009|Edward Kirk]] bravely volunteered to fix the picture.
[[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.
 
Finally, the group discussed creating SOPs (Standard Operating Procedures) for Bugzappers, along the lines of those already used by the Infrastructure group. [[User:Poelstra|John Poelstra]] proposed the first SOP cover the procedure for gaining membership in the Bugzappers, and further proposed that it should involve the prospective new member posting a self-introduction email to the mailing list. [[User:Beland|Christopher Beland]] and [[User:Tk009|Edward Kirk]] opposed this as they were worried that some new members would not feel comfortable posting such a message, particularly if it contained personal information. The group agreed to discuss the proposal further on the mailing list.
 
The next QA weekly meeting will be held on 2009-03-11 at 1700 UTC (note changed time, in UTC reference frame) in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-03-10 at 1500 UTC in #fedora-meeting.
 
<references/>
 
=== Bugzappers Wiki Re-organization ===
 
[[User:Beland|Christopher Beland]] made several proposals<ref>http://www.redhat.com/archives/fedora-test-list/2009-February/msg01223.html</ref> on reorganizing the Bugzappers wiki area. This prompted a long discussion. In the end, Christopher was asked to provide drafts for several of his proposed changes for the group to evaluate. Both Christopher and [[User:Tk009|Edward Kirk]] provided drafts for a new front page. [[User:Adamwill|Adam Williamson]] commented<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00290.html</ref> that both drafts had good elements, and offered to create a new draft to try and combine the two.
 
<references/>


=== 20 Second Boot Test Day Follow-up ===
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.


[[User:Harald|Harald Hoyer]] posted a follow-up email<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00057.html</ref> on the previously-held 20 Second Boot test day<ref>https://fedoraproject.org/wiki/QA/Test_Days/2009-02-19</ref>, pointing to a blog post<ref>http://www.harald-hoyer.de/personal/blog/20_Seconds_Boot_Feature_Test_Day</ref> where he summarized all the useful data he was able to get from the test day.
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/>
<references/>


=== Bugzappers Meeting Schedule ===
=== Bugzappers Wiki reorganization ===


Lalit Dhiri proposed<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00131.html</ref> having a second meeting to accommodate those whose schedules made it impossible for them to attend the regular group meetings. [[User:Adamwill|Adam Williamson]] said<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00155.html</ref> that was not likely to be practical, but suggested that the meeting time could be moved if a time when more group members would be able to attend could be identified. [[User:laubersm|Susan Lauber]] suggested<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00165.html</ref> using the Wiki's meeting matrix template to handle registering who is available when, and set up a Wiki page<ref>https://fedoraproject.org/wiki/Bugzappers_meeting_matrix</ref> for the purpose.
[[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>.


<references/>
<references/>


=== Ubuntu Triage Discussion ===
=== Advertising triage days ===


[[User:Pfrields|Paul Frields]] pointed out<ref>https://www.redhat.com/archives/fedora-test-list/2009-March/msg00211.html</ref> a long discussion on the topic of bug triaging in Ubuntu<ref>http://lwn.net/Articles/321473/</ref>, and wondered what the lessons for the Bugzappers might be. [[User:Adamwill|Adam Williamson]] suggested that it showed it is important for triagers to follow up on bugs they triage, rather than just touching them once and then never returning, which can leave the reporter more frustrated than if the bug had never been triaged at all. In the ensuing discussion, John Summerfield suggested that triagers should try to cover one area of which they had substantial knowledge rather than attempting to cover all bugs in all components<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00312.html</ref>, and that the Bugzappers group should remember actively to involve package maintainers in the triaging process<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00385.html</ref>. [[User:kkofler|Kevin Kofler]] explained<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00393.html</ref> that, within the KDE SIG, maintainers and triagers do work together and communicate via IRC.
[[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.


<references/>
<references/>


=== Introduction Emails ===
=== Metrics ===


[[User:Adamwill|Adam Williamson]] mooted the proposal from the weekly meeting that introduction emails be required for new group members<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00266.html</ref>. [[User:Poelstra|John Poelstra]] supported the proposal<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00314.html</ref>, as did [[User:Tk009|Edward Kirk]]<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00319.html</ref>. [[User:Beland|Christopher Beland]] suggested<ref>http://www.redhat.com/archives/fedora-test-list/2009-March/msg00341.html</ref>that anyone who became active on the mailing list but did not write a formal self-introduction email should also be accepted.
[[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.


<references/>
<references/>

Revision as of 01:10, 14 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's regular test day[1] was on the Intel graphics card driver, particularly kernel mode setting[2]. 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.

Next week will be special, as two test days are scheduled. A special test day is planned for Tuesday[3], on DeviceKit[4] - 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[5] will be on the Xfce desktop environment[6], 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.

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!

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

Weekly meetings

The QA group weekly meeting[1] was held on 2009-03-11. The full log is available[2]. After a bracing discussion on how to send an apparently empty line to IRC, 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. Adam Williamson noted that he had discussed one such suite, rendercheck, with 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.

Jesse Keating and 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.

Adam Williamson reported that he and 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.

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.

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

The Bugzappers group weekly meeting[3] was held on 2009-03-10. The full log is available[4]. 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.

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. Edward Kirk volunteered to write up this procedure into an SOP, as discussed at the previous meeting.

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 Adam Williamson to finish his combination of Edward Kirk's draft[5] and Christopher Beland's draft[6], 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 [7]), and agreed it was a good layout, but some of the content that had been merged into it should not have been. Adam Williamson suggested that the statistics be updated regularly and automatically via Brennan Ashton's metrics script.

Edward Kirk reported that he had updated the bug workflow graphic[8] 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 potential new meeting time with reference to the availability matrix[9], 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.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings
  2. ↑ http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090311.log.html
  3. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
  4. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-10
  5. ↑ https://fedoraproject.org/wiki/User:Tk009/bugzappers
  6. ↑ https://fedoraproject.org/wiki/User:Beland/BugZappers
  7. ↑ https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
  8. ↑ http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
  9. ↑ https://fedoraproject.org/wiki/Bugzappers_meeting_matrix

Bugzappers Wiki reorganization

Christopher Beland worked hard to revise several areas of the Wiki, including a new Tracking page[1] which combined pages on active triagers, priority triage components, group goals and finding bugs[2]. After feedback from Edward Kirk, John Poelstra and others, this was reduced simply to the Components and Triagers page[3], leaving the others separate for now. Christopher updated these pages also. Adam Williamson submitted his combined new front page draft for the group's review[4].

  1. ↑ https://fedoraproject.org/wiki/BugZappers/Tracking
  2. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00437.html
  3. ↑ https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
  4. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00662.html

Advertising triage days

Christopher Beland pointed out that triage days are not advertised anywhere in the Wiki[1]. Adam Williamson apologized and explained[2] 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.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00695.html
  2. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00713.html

Metrics

Christopher Beland reported[1] that he could not access the pages for Brennan Ashton's triage metrics reporting system. Brennan thanked him for the feedback[2] and explained that there was a hardware issue on the server. John Poelstra suggested[3] that the code for the metric system be hosted in the Bugzappers group's git repository.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00693.html
  2. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00727.html
  3. ↑ http://www.redhat.com/archives/fedora-test-list/2009-March/msg00739.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=90551"