From Fedora Project Wiki

< FWN‎ | Beats

(create 199 qa beat)
(create 200 qa beat (sorry it's late!))
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


Last week's first Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-20</ref> was on the confined SELinux users feature. The modest turnout of testers managed to run through nearly the whole set of tests and expose several bugs to help refine the feature. The second Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-22</ref> was on power management<ref>https://fedoraproject.org/wiki/Features/PowerManagementF12</ref> improvements in Fedora 12. A good turnout of testers ran the carefully prepared test suite on an even wider array of machines, providing valuable data for the developers.
Last week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-29</ref> was on internationalization (also known as i18n)<ref>http://fedoraproject.org/wiki/I18N</ref>. We had a good turnout of testers who covered a wide variety of languages and input methods. In general many appear to be in good shape, but the testing turned up several issues in Bengali, Malayalam and a few other languages. This testing will help us to improve the implementation of these languages in future. [[User:Rhe|Rui He]] provided a summary<ref>https://www.redhat.com/archives/fedora-test-list/2009-November/msg00038.html</ref> of the event, including a list of all bugs filed.


Next week's Test Day<ref>https://fedoraproject.org/wiki/Test_Day:2009-10-29</ref>, the last of the Fedora 12 cycle, will be on internationalization (also known as i18n)<ref>http://fedoraproject.org/wiki/I18N</ref> - an event which usually has a strong focus on input methods, but can also cover issues like fonts. This Test Day was previously scheduled for 2009-10-15 but was postponed, this is the new date. The Test Day will run all day on Thursday 2009-10-29 in the #fedora-test-day IRC channel. Please come along and help ensure Fedora works just as well no matter what language you use!
No Test Day is planned for next week. If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>http://fedorahosted.org/fedora-qa/</ref>.
 
No Fit and Finish track Test Day is planned for next week.
 
If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>http://fedorahosted.org/fedora-qa/</ref>.


<references/>
<references/>
Line 22: Line 18:
=== Weekly meetings ===
=== Weekly meetings ===


The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-10-19. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-10-19/fedora-meeting.2009-10-19-15.58.log.html</ref>. [[User:Jlaska|James Laska]] followed up on concerns raised at the last meeting by [[User:jkeating|Jesse Keating]] that blocker bugs may not be being identified fast enough. James noted that research by himself and [[User:Adamwill|Adam Williamson]] indicated almost all issues had been escalated within two days of being identified, which he felt was a good record.
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-10-26. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-10-26/fedora-meeting.2009-10-26-16.08.log.html</ref>. [[User:Jlaska|James Laska]] reported that he had renamed most of the Debugging pages<ref>http://fedoraproject.org/wiki/Category:Debugging</ref> to follow the previously agreed-upon naming scheme. The only remaining page was KernelBugTriage, and he would check with kernel maintainers before renaming this one.
 
[[User:Jlaska|James Laska]] had also investigated the packaging of the israwhidebroken.com project code. He found it was very easy to build a package since the code used Python setuptools. He also reported that he had requested the creation of a public autoqa-devel mailing list for the AutoQA project<ref>https://fedorahosted.org/fedora-infrastructure/ticket/1733</ref>.
 
[[User:Jlaska|James Laska]] initiated a review of the Beta testing process. [[User:Liam|Liam Li]] was thinking about ways to get 100% installation test case coverage, or at least improve the coverage to all tier 2 tests. James was pleased that all tier 1 tests had been covering during the Beta test process. James asked whether it would be possible to reduce the number of tests in the matrix. Liam was not sure whether that would actually reduce release quality. James suggested looking for potential duplication of cases in the matrix. [[User:Adamwill|Adam Williamson]] wondered if it would be possible to generate a version of the matrix showing only uncompleted tests, so it would be clearer which tests still needed to be performed. James pointed out that the matrix could already be sorted. Adam had not considered that possibility, and suggested that it be explained in Liam's test request emails. Ben Williams pointed out the Fedora Unity test matrix<ref>http://spins.fedoraunity.org/Members/Southern_Gentleman/Fedora%2012%20%20beta%20TestMatrix</ref>, and James suggested merging the two together. [[User:Wwoods|Will Woods]] discussed the possibility of integrating the AutoQA installation test results; he said it would be simpler to just have a link to an external AutoQA results page, but having the AutoQA system insert results into a Wiki page would be possible.


[[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] reported on the progress of the AutoQA project. Will had been working on getting the production AutoQA instance up and running. He had given up on the idea of having israwhidebroken.com link back to detailed test results, instead planning to provide a page explaining where to find the results. This means israwhidebroken.com can go up as soon as the production AutoQA instance is running. Beyond this, Will has been working on a hook for Koji, which will allow AutoQA to trigger on new builds in Koji. A preliminary version of this code is available<ref>https://fedorahosted.org/autoqa/browser/hooks/post-koji-build/watch-koji-builds.py</ref>. Kamil had continued work on his script to monitor important changes in packages, now renamed 'rpmguard'. It is now maintained in AutoQA git<ref>http://git.fedorahosted.org/git/autoqa.git?a=tree;f=tests/rpmguard</ref>. He had created test packages to make sure the script works as intended, and now is looking for feedback from a wider test audience. He planned to write a blog post to try and trigger people to test and provide feedback on the script. He was also looking for suggestions for the best possible output format for the tool.
[[User:Jlaska|James Laska]] noted that Marcela Maslanova had written automated testing scripts for the previous week's Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-22</ref>, and this had produced a very positive experience. He asked the group to think about what future Test Days could potentially benefit from testing automation in this way.


[[User:Johannbg|Jóhann Guðmundsson]] and [[User:Adamwill|Adam Williamson]] updated the status of the project to revise debugging-related pages. [[User:Rjune|Richard June]] had helped out by starting work on an alternative template page<ref>http://fedoraproject.org/wiki/Template:How_to_debug2</ref>. Adam felt it should be possible to come up with a template which would standardize the layout of such pages while still providing enough flexibility to cover different components, but he had not yet had enough time to try and work on this himself. He emphasized that no-one should wait on the planned template before revising pages to fit the new format and naming scheme. [[User:Jlaska|James Laska]] volunteered to work on renaming all existing pages to fit the new naming scheme.
[[User:Adamwill|Adam Williamson]] passed along a proposal from Milos Jakubicek that the QA and BugZappers group help with filing bugs on the remaining Fedora 12 packages with FTBFS (fails to build from scratch) issues. [[User:jkeating|Jesse Keating]] pointed out that [[User:Mdomsch|Matt Domsch]] has a script which tries to rebuild all of Rawhide and automatically files bugs on packages which fail, which he typically runs once per cycle. Jesse believed the fact that Milos is aware of several packages which fail to build but for which no bug report currently exists is a result of the fact that the list Milos is working from was generated a month after Matt's latest test run. The group agreed that Adam would ask Milos to clarify his proposal and see if it was still necessary in light of the existence of Matt's script.


[[User:jkeating|Jesse Keating]] asked the group to help review tag requests for the final release. He noted there was no formal set of requirements for tag requests for critical path packages, but asked reviewers to be sensible in judging whether the change was safe and genuinely necessary. Requests should explain what issue the updated package fixes, why it needs to be fixed, and the likely impact if it is not fixed. He provided an RSS feed<ref>https://fedorahosted.org/rel-eng/timeline?ticket=on&changeset=on&milestone=on&wiki=on&max=50&daysback=90&format=rss</ref> to monitor tickets as they come in.  
[[User:Johannbg|Jóhann Guðmundsson]] presented his proposal for an automated test of non-U.S. locale installation, prompted by the significant bugs<ref>http://bugzilla.redhat.com/show_bug.cgi?id=528317</ref> <ref>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=530452</ref> in the Beta with installations with different locale settings which were not caught by pre-release testing. He pointed out that implementing such a test would be relatively simple and involve only defining a non-U.S. locale in a kickstart file for an installation test run. The group agreed that this would be valuable testing and asked Jóhann to write it up into a test case that could be added to the installation test matrix and also potentially automated as part of future AutoQA development.


[[User:Adamwill|Adam Williamson]] asked the group to help develop the Fedora 12 Common Bugs page<ref>http://fedoraproject.org/wiki/Common_F12_bugs</ref> by adding issues to it and marking bugs which should be added to it with the CommonBugs keyword. [[User:Jlaska|James Laska]] provided a search URL<ref>http://tinyurl.com/l4kma5</ref> for listing bug reports marked as needing to be added to a Common Bugs page.
[[User:Wwoods|Will Woods]] and [[User:Kparal|Kamil Paral]] reported on the progress of the AutoQA project. Kamil had made a blog post announcing rpmguard to the world<ref>http://kparal.wordpress.com/2009/10/21/rpmguard-print-important-differences-between-rpms</ref>. He had received feedback from several people, including suggestions from [[User:Skvidal|Seth Vidal]] and [[User:atorkhov|Alexey Torkhov]] (whose feedback had prompted a ticket<ref>http://fedorahosted.org/autoqa/ticket/75</ref>). Kamil is now planning to work on integrating rpmguard into AutoQA with the help of the newly-implemented Koji watcher, which allows AutoQA to pick up - and potentially trigger tests upon - every new build which goes through Koji. Will briefly touched upon the future organization plan for all the AutoQA code, based around a library for the server-side parts such as watchers and another library for actual tests, along with separate configuration files for things like the relationships between Koji tags, so these configuration details can be separated from the main functional code. Will also noted that he had created a Python script for generating the current set of critical path packages<ref>http://wwoods.fedorapeople.org/files/critical-path/critpath.py</ref>: simply running it generates the list as critpath.txt. He plans to have this integrated into the Rawhide compose process so that a daily updated critical path package list is always available at a static URL. Finally, Will noted that a public mailing list has been created for the AutoQA project, autoqa-devel<ref>http://fedorahosted.org/mailman/listinfo/autoqa-devel</ref>. [[User:Jlaska|James Laska]] noted in passing that the hardware for the production AutoQA instance was currently likely to be delivered on 2009-11-20.


The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-10-20. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-10-20/fedora-meeting.2009-10-20-15.10.log.html</ref>. [[User:Rjune|Richard June]] reported on the progress of the kernel triage project. He had found more bugs that required further information, and was working with [[User:linville|John Linville]] to ensure his process for getting more information on these reports was correct.
[[User:Jlaska|James Laska]] reviewed upcoming events. He noted that preparation for the then-upcoming i18n Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-29</ref> was well advanced, and asked for group members to help out with testing if they could. He trailed the then-upcoming second Fedora 12 blocker bug review day, which would take place on 2009-10-30, and [[User:Adamwill|Adam Williamson]] asked people to help by re-testing blocker bugs prior to the event and coming to the event to help walk the list.


[[User:Adamwill|Adam Williamson]] provided an update on the debugging page revision project, recapping the discussion from the previous day's QA meeting.
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-10-27. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-10-27/fedora-meeting.2009-10-27-15.09.log.html</ref>. [[User:Tk009|Edward Kirk]] asked if there was a firm date yet set for the semantics switchover (marking triaged bugs as NEW with the Triaged keyword rather than ASSIGNED). [[User:Adamwill|Adam Williamson]] looked at the schedule and noted it should be around 2009-11-12 if no further schedule changes occurred.


[[User:Tk009|Edward Kirk]] made a suggestion for a Triage Day event. He suggested a day to review all remaining open Fedora 10 bugs, trying to close reports that can be closed and rebase others to later Fedora releases if possible and necessary. The group liked the idea, and there was general agreement on Friday 2009-10-30 at 15:00 UTC as the date and time. Edward promised to announce the event on the mailing list ahead of time.
No-one had heard from Brennan Ashton regarding his promised summary of the status of the triage metrics project.


Brennan Ashton updated the status of the triage metrics project. He had not had time to work on it since his last update. He had tried to find someone to help maintain the project, but had not yet been successful. However, he had the upcoming week off and would try to produce a summary of the current state of the project to make it easier to find other maintainers. [[User:Adamwill|Adam Williamson]] and [[User:Tk009|Edward Kirk]] were eager to try and help move the project forward.
[[User:Tk009|Edward Kirk]] wondered if the bug workflow page and diagram<ref>http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow</ref> would require updating when the semantics change occurred. [[User:Adamwill|Adam Williamson]] believed it would, but the necessary changes would be quite minor. Edward and Adam agreed to keep the necessary changes in mind for the meeting prior to the semantics change.


[[User:StevenParrish|Steven Parrish]] asked if any other group members would be at the upcoming FUDCon Toronto event<ref>http://fedoraproject.org/wiki/FUDCon:Toronto_2009</ref>. [[User:Adamwill|Adam Williamson]] said that he and the rest of the Red Hat Fedora QA team would be there. Steven and Adam noted that limited funding was available for community members to attend the event, and explained that those wanting funding should add their name to the attendee list and check the column for funding. Brennan Ashton asked if anyone else would be driving from Boston. Adam pointed out that there was a group bus<ref>http://fedoraproject.org/wiki/FUDCon:Toronto_2009#Bus_Travel</ref> being organized.
[[User:Tk009|Edward Kirk]] promised to make sure the email warning developers that the regular housekeeping changes in Bugzilla at release time would be coming soon.


The next QA weekly meeting will be held on 2009-10-26 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-10-27 at 1500 UTC in #fedora-meeting.
The next QA weekly meeting will be held on 2009-11-02 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-11-03 at 1500 UTC in #fedora-meeting. Note that the meeting times in UTC do not change even though many countries are going through daylight savings time changes around this time of year, with the result that the meetings will be one hour earlier for many people in practice.


<references/>
<references/>


=== Fedora 12 Beta release ===
=== Fedora 12 testing ===


Of course, the week's big news was the release of Fedora 12 Beta<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00393.html</ref>. This prompted several threads<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00453.html</ref> <ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00458.html</ref> <ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00486.html</ref> <ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00493.html</ref> (and more) from enthusiastic testers, with valuable experiences which [[User:Adamwill|Adam Williamson]] encouraged to be turned into bug reports.
Much of the week's mailing list activity centred on testing the Fedora 12 Beta and post-beta updates, with much valuable testing being performed by many volunteers. [[User:Adamwill|Adam Williamson]] asked<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00650.html</ref> for group members to provide feedback on the latest accepted kernel build, which had incorporated several changes from the kernel shipped in the Beta release. Many testers replied with helpful confirmation that the new kernel worked well. [[User:Liam|Liam Li]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00721.html</ref> the pre-RC install testing cycle and associated test matrix<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_12_Pre-RC_Install</ref>, asking group members to try and cover as much of the install test case set as possible before the release candidate phase began on 2009-11-04; he later provided a report<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00816.html</ref> on this testing. Adam requested testing<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00805.html</ref> of an ext4 data corruption issue<ref>http://bugzilla.kernel.org/show_bug.cgi?id=14354</ref> which had surfaced in upstream kernel 2.6.32 testing to try and ensure that it was not affecting the 2.6.31 kernel included in Fedora 12.  


<references/>
<references/>


=== Confined users Test Day summary ===
=== Blocker bug review ===


Eduard Benes provided a summary<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00488.html</ref> of the SELinux confined users Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-20</ref>, listing the bug reports resulting from the Test Day and thanking the testers and also [[User:dwalsh|Dan Walsh]], who had already begun resolving reported bugs.
The second Fedora 12 blocker bug review meeting took place on Friday 2009-11-30, and [[User:Adamwill|Adam Williamson]] posted a summary<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00845.html</ref>. He noted that all remaining 43 blocker bugs had been reviewed, linked to the meeting summary<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2009-10-30/fedora-bugzappers.2009-10-30-15.01.html</ref> which outlined the status for each bug, and thanked the many members of the QA, release engineering and development groups who had contributed to the meeting.


<references/>
<references/>


=== Fedora 12 blocker bug review meeting ===
=== Fedora 10 bug review event ===


[[User:Adamwill|Adam Williamson]] provided a recap<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00579.html</ref> of the blocker bug review meeting which took place on Friday 2009-10-23, linking to a report<ref>http://meetbot.fedoraproject.org/fedora-bugzappers/2009-10-23/fedora-bugzappers.2009-10-23-15.00.html</ref> of the meeting which lists the status and actions decided for all 51 blocker bugs reviewed during the course of the meeting. He thanked all those who attended for their help in reviewing the large load of bugs.
[[User:Tk009|Edward Kirk]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00791.html</ref> a BugZappers event on 2009-10-30 at which the group would gather to try and review remaining Fedora 10 bugs and see which could be either closed or promoted to Fedora 11 or 12, prior to the automated closing of these bugs as old when Fedora 12 is released.


<references/>
<references/>

Revision as of 20:55, 2 November 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

Last week's Test Day[1] was on internationalization (also known as i18n)[2]. We had a good turnout of testers who covered a wide variety of languages and input methods. In general many appear to be in good shape, but the testing turned up several issues in Bengali, Malayalam and a few other languages. This testing will help us to improve the implementation of these languages in future. Rui He provided a summary[3] of the event, including a list of all bugs filed.

No Test Day is planned for next week. If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[4].

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-29
  2. ↑ http://fedoraproject.org/wiki/I18N
  3. ↑ https://www.redhat.com/archives/fedora-test-list/2009-November/msg00038.html
  4. ↑ http://fedorahosted.org/fedora-qa/

Weekly meetings

The QA group weekly meeting[1] was held on 2009-10-26. The full log is available[2]. James Laska reported that he had renamed most of the Debugging pages[3] to follow the previously agreed-upon naming scheme. The only remaining page was KernelBugTriage, and he would check with kernel maintainers before renaming this one.

James Laska noted that Marcela Maslanova had written automated testing scripts for the previous week's Test Day[4], and this had produced a very positive experience. He asked the group to think about what future Test Days could potentially benefit from testing automation in this way.

Adam Williamson passed along a proposal from Milos Jakubicek that the QA and BugZappers group help with filing bugs on the remaining Fedora 12 packages with FTBFS (fails to build from scratch) issues. Jesse Keating pointed out that Matt Domsch has a script which tries to rebuild all of Rawhide and automatically files bugs on packages which fail, which he typically runs once per cycle. Jesse believed the fact that Milos is aware of several packages which fail to build but for which no bug report currently exists is a result of the fact that the list Milos is working from was generated a month after Matt's latest test run. The group agreed that Adam would ask Milos to clarify his proposal and see if it was still necessary in light of the existence of Matt's script.

Jóhann Guðmundsson presented his proposal for an automated test of non-U.S. locale installation, prompted by the significant bugs[5] [6] in the Beta with installations with different locale settings which were not caught by pre-release testing. He pointed out that implementing such a test would be relatively simple and involve only defining a non-U.S. locale in a kickstart file for an installation test run. The group agreed that this would be valuable testing and asked Jóhann to write it up into a test case that could be added to the installation test matrix and also potentially automated as part of future AutoQA development.

Will Woods and Kamil Paral reported on the progress of the AutoQA project. Kamil had made a blog post announcing rpmguard to the world[7]. He had received feedback from several people, including suggestions from Seth Vidal and Alexey Torkhov (whose feedback had prompted a ticket[8]). Kamil is now planning to work on integrating rpmguard into AutoQA with the help of the newly-implemented Koji watcher, which allows AutoQA to pick up - and potentially trigger tests upon - every new build which goes through Koji. Will briefly touched upon the future organization plan for all the AutoQA code, based around a library for the server-side parts such as watchers and another library for actual tests, along with separate configuration files for things like the relationships between Koji tags, so these configuration details can be separated from the main functional code. Will also noted that he had created a Python script for generating the current set of critical path packages[9]: simply running it generates the list as critpath.txt. He plans to have this integrated into the Rawhide compose process so that a daily updated critical path package list is always available at a static URL. Finally, Will noted that a public mailing list has been created for the AutoQA project, autoqa-devel[10]. James Laska noted in passing that the hardware for the production AutoQA instance was currently likely to be delivered on 2009-11-20.

James Laska reviewed upcoming events. He noted that preparation for the then-upcoming i18n Test Day[11] was well advanced, and asked for group members to help out with testing if they could. He trailed the then-upcoming second Fedora 12 blocker bug review day, which would take place on 2009-10-30, and Adam Williamson asked people to help by re-testing blocker bugs prior to the event and coming to the event to help walk the list.

The Bugzappers group weekly meeting[12] was held on 2009-10-27. The full log is available[13]. Edward Kirk asked if there was a firm date yet set for the semantics switchover (marking triaged bugs as NEW with the Triaged keyword rather than ASSIGNED). Adam Williamson looked at the schedule and noted it should be around 2009-11-12 if no further schedule changes occurred.

No-one had heard from Brennan Ashton regarding his promised summary of the status of the triage metrics project.

Edward Kirk wondered if the bug workflow page and diagram[14] would require updating when the semantics change occurred. Adam Williamson believed it would, but the necessary changes would be quite minor. Edward and Adam agreed to keep the necessary changes in mind for the meeting prior to the semantics change.

Edward Kirk promised to make sure the email warning developers that the regular housekeeping changes in Bugzilla at release time would be coming soon.

The next QA weekly meeting will be held on 2009-11-02 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-11-03 at 1500 UTC in #fedora-meeting. Note that the meeting times in UTC do not change even though many countries are going through daylight savings time changes around this time of year, with the result that the meetings will be one hour earlier for many people in practice.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings
  2. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-10-26/fedora-meeting.2009-10-26-16.08.log.html
  3. ↑ http://fedoraproject.org/wiki/Category:Debugging
  4. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-22
  5. ↑ http://bugzilla.redhat.com/show_bug.cgi?id=528317
  6. ↑ http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=530452
  7. ↑ http://kparal.wordpress.com/2009/10/21/rpmguard-print-important-differences-between-rpms
  8. ↑ http://fedorahosted.org/autoqa/ticket/75
  9. ↑ http://wwoods.fedorapeople.org/files/critical-path/critpath.py
  10. ↑ http://fedorahosted.org/mailman/listinfo/autoqa-devel
  11. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-29
  12. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
  13. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-10-27/fedora-meeting.2009-10-27-15.09.log.html
  14. ↑ http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow

Fedora 12 testing

Much of the week's mailing list activity centred on testing the Fedora 12 Beta and post-beta updates, with much valuable testing being performed by many volunteers. Adam Williamson asked[1] for group members to provide feedback on the latest accepted kernel build, which had incorporated several changes from the kernel shipped in the Beta release. Many testers replied with helpful confirmation that the new kernel worked well. Liam Li announced[2] the pre-RC install testing cycle and associated test matrix[3], asking group members to try and cover as much of the install test case set as possible before the release candidate phase began on 2009-11-04; he later provided a report[4] on this testing. Adam requested testing[5] of an ext4 data corruption issue[6] which had surfaced in upstream kernel 2.6.32 testing to try and ensure that it was not affecting the 2.6.31 kernel included in Fedora 12.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00650.html
  2. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00721.html
  3. ↑ http://fedoraproject.org/wiki/Test_Results:Fedora_12_Pre-RC_Install
  4. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00816.html
  5. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00805.html
  6. ↑ http://bugzilla.kernel.org/show_bug.cgi?id=14354

Blocker bug review

The second Fedora 12 blocker bug review meeting took place on Friday 2009-11-30, and Adam Williamson posted a summary[1]. He noted that all remaining 43 blocker bugs had been reviewed, linked to the meeting summary[2] which outlined the status for each bug, and thanked the many members of the QA, release engineering and development groups who had contributed to the meeting.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00845.html
  2. ↑ http://meetbot.fedoraproject.org/fedora-bugzappers/2009-10-30/fedora-bugzappers.2009-10-30-15.01.html

Fedora 10 bug review event

Edward Kirk announced[1] a BugZappers event on 2009-10-30 at which the group would gather to try and review remaining Fedora 10 bugs and see which could be either closed or promoted to Fedora 11 or 12, prior to the automated closing of these bugs as old when Fedora 12 is released.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00791.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=133638"