From Fedora Project Wiki

< FWN‎ | Beats

(create 198 qa beat)
(create 199 qa beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


Last week's planned Test Day on internationalization (i18n) was postponed to a yet-to-be-determined future date. Our apologies to anyone who made time to attend.
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.


Two Test Days are scheduled for next week. The first<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-20</ref> is on the confined SELinux users feature. This feature involves assigning an SELinux role to a user. The role's policy controls the extent of the user's access to the system. The Test Day will focus on testing several scenarios to ensure the policy restrictions work as they should. As usual, there will be a live CD available for testing - there's no need to install Rawhide. The Test Day will run all day on Thursday 2009-10-20 in the #fedora-test-day IRC channel.
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!
 
The second Test Day<ref>http://fedoraproject.org/wiki/Test_Day:2009-10-22</ref> will be on power management<ref>https://fedoraproject.org/wiki/Features/PowerManagementF12</ref>, especially specific improvements made in Fedora 12. Some very specific but easy-to-run test cases which will greatly aid the development team in refining power management have been developed for the Test Day: there's even a helpful script which runs the tests and generates the need results automatically. As usual, there will be a live CD available for testing - there's no need to install Rawhide. This Test Day will be very easy to participate in, and the information you can generate will be very helpful, so please come along and help out! The Test Day will run all day on Thursday 2009-10-22 in the #fedora-test-day IRC channel.


No Fit and Finish track Test Day is planned for next week.
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 12 or 13 cycles, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>http://fedorahosted.org/fedora-qa/</ref>.
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 24: Line 22:
=== Weekly meetings ===
=== Weekly meetings ===


The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-10-12. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-10-12/fedora-meeting.2009-10-12-16.00.log.html</ref>. [[User:Jlaska|James Laska]] reported that the new hardware which would be used to host the israwhidebroken.com project and other parts of the AutoQA project is in transit.
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.
 
[[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: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: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: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:Jlaska|James Laska]] had contacted the Anaconda development team to check if the recent installer test days had identified any Beta blocker bugs. He found that the first test day had resulted in three blockers being added to the list. [[User:jkeating|Jesse Keating]] worried that too much testing was being done after the Beta freeze, which made resolving identified bugs very difficult. James felt that extensive testing was being done both before and after the freeze. Jesse believed some of the blocker bugs that were found after the freeze date could have been found earlier. James agreed to investigate the bugs in question to see when they were introduced and when they were identified.
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 the status of the first Beta release candidate build, and noted status on the last remaining beta blocker bug was unclear. Denise Dumas said that [[User:Dlehman|Dave Lehman]] would investigate and report whether the bug was fixed in the release candidate build, and hence whether a second release candidate build would be required. James, [[User:Liam|Liam Li]] and [[User:Rhe|Rui He]] had already started validation testing on the release candidate build<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_12_Beta_RC1_Install</ref>.
[[User:Adamwill|Adam Williamson]] provided an update on the debugging page revision project, recapping the discussion from the previous day's QA meeting.


[[User:Wwoods|Will Woods]] reported on the progress of the AutoQA project. He had been working on backlinking from the test status information on israwhidebroken.com to the actual test result in the autotest front end, but had not yet found a satisfactory solution. He had also been looking at auto-generating a Wiki page to list the critical path packages (as the set of critical path packages can change unpredictably, a manually-maintained static page is not a good solution). His plan for this is blocked by the Python interface to the Wiki using JSON, which cannot create or edit pages. Will and [[User:Jlaska|James Laska]] agreed that James would work on creating a package of the israwhidebroken.com code to be used for the production instance of the site. [[User:Kparal|Kamil Paral]] reported steady progress on his packagediff test for identifying major changes between package versions. He had initial implementations of most important tests, and was working to generate fake packages so he can test the script and isolate any bugs in it. The group agreed that in the long term it would make sense to integrate Kamil's work as extensions to the existing rpmdiff tool, but in the short term it could be hosted as part of the AutoQA project.
[[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.


[[User:Johannbg|Jóhann Guðmundsson]] explained his project to revise and standardize Wiki pages dealing with debugging and reporting bugs in various components<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00112.html</ref>. He had created a template for such pages<ref>http://fedoraproject.org/wiki/Template:How_to_debug</ref> and revised several existing pages to fit this new template. The group discussed a standard naming convention for such pages, and agreed on How_to_debug_(component name). Jóhann mentioned that he would welcome feedback on the usefulness of the existing pages, which would be the most important ones to revise, and what new pages of this type should be created.
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.


The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-10-13. [[User:Adamwill|Adam Williamson]] commented on the QA group's discussion of [[User:Johannbg|Jóhann Guðmundsson's]] debugging page revision project, noting the agreement on the How_to_debug_(component name) naming convention.
[[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]] noted that housekeeping tasks, which would have been starting that week, had been delayed due to the overall release schedule delay occasioned by the delay of the Beta release.
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.


[[User:Adamwill|Adam Williamson]] noted that [[User:Rjune|Richard June]] was not present to give an update on the kernel triage project, nor was Brennan Ashton present to discuss the triage metrics project.
<references/>


[[User:Rudchenkos|Sergey Rudchenko]] wanted to know if there was a way to have Bugzilla notify him of new bugs being filed on a particular component, but not of any change activity to existing bugs, as he found the volume of email with all the change messages included overwhelming. [[User:Tk009|Edward Kirk]] suggested that he use the RSS feed search result feature for this. Any Bugzilla search can be used as an RSS feed in Red Hat's Bugzilla, so to achieve the desired result you can simply search for NEW bugs in any component and subscribe to the feed for the search result. New bugs for that component will then be shown on the feed.
=== Fedora 12 Beta release ===


The next QA weekly meeting will be held on 2009-10-19 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-10-20 at 1500 UTC in #fedora-meeting.
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.


<references/>
<references/>


=== DeltaISO update ===
=== Confined users Test Day summary ===


Andre Robatino reported<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00197.html</ref> that he was unable to generate DeltaISOs on Rawhide as a side-effect of the endianness issue in xz which had been previously discussed by the development group. Andre later announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00222.html</ref> DeltaISOs for Beta test compose -> Beta RC1 and Beta RC1 -> Beta RC2.
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.


<references/>
<references/>


=== Fedora 12 Beta RC2 testing ===
=== Fedora 12 blocker bug review meeting ===


[[User:Liam|Liam Li]] announced the formal testing process for the second release candidate build of Fedora 12 Beta<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00203.html</ref>. He noted that the test matrix was available<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_12_Beta_RC2_Install</ref> and asked for the group's help in performing as many of the tests as possible. Cornel Panceac wondered<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00260.html</ref> why there were no live images available. [[User:jkeating|Jesse Keating]] explained<ref>http://www.redhat.com/archives/fedora-test-list/2009-October/msg00290.html</ref> that he had had to delay building the live images until he was sure the regular installer images were OK due to resource constraints.
[[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.


<references/>
<references/>

Revision as of 01:57, 26 October 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 first Test Day[1] 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[2] was on power management[3] 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.

Next week's Test Day[4], the last of the Fedora 12 cycle, will be on internationalization (also known as i18n)[5] - 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 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[6].

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-20
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-22
  3. ↑ https://fedoraproject.org/wiki/Features/PowerManagementF12
  4. ↑ https://fedoraproject.org/wiki/Test_Day:2009-10-29
  5. ↑ http://fedoraproject.org/wiki/I18N
  6. ↑ http://fedorahosted.org/fedora-qa/

Weekly meetings

The QA group weekly meeting[1] was held on 2009-10-19. The full log is available[2]. James Laska followed up on concerns raised at the last meeting by Jesse Keating that blocker bugs may not be being identified fast enough. James noted that research by himself and Adam Williamson indicated almost all issues had been escalated within two days of being identified, which he felt was a good record.

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[3].

James Laska initiated a review of the Beta testing process. 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. 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[4], and James suggested merging the two together. 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.

Will Woods and 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[5]. Kamil had continued work on his script to monitor important changes in packages, now renamed 'rpmguard'. It is now maintained in AutoQA git[6]. 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.

Jóhann Guðmundsson and Adam Williamson updated the status of the project to revise debugging-related pages. Richard June had helped out by starting work on an alternative template page[7]. 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. James Laska volunteered to work on renaming all existing pages to fit the new naming scheme.

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[8] to monitor tickets as they come in.

Adam Williamson asked the group to help develop the Fedora 12 Common Bugs page[9] by adding issues to it and marking bugs which should be added to it with the CommonBugs keyword. James Laska provided a search URL[10] for listing bug reports marked as needing to be added to a Common Bugs page.

The Bugzappers group weekly meeting[11] was held on 2009-10-20. The full log is available[12]. Richard June reported on the progress of the kernel triage project. He had found more bugs that required further information, and was working with John Linville to ensure his process for getting more information on these reports was correct.

Adam Williamson provided an update on the debugging page revision project, recapping the discussion from the previous day's QA meeting.

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.

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. Adam Williamson and Edward Kirk were eager to try and help move the project forward.

Steven Parrish asked if any other group members would be at the upcoming FUDCon Toronto event[13]. 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[14] being organized.

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.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings
  2. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-10-19/fedora-meeting.2009-10-19-15.58.log.html
  3. ↑ https://fedorahosted.org/fedora-infrastructure/ticket/1733
  4. ↑ http://spins.fedoraunity.org/Members/Southern_Gentleman/Fedora%2012%20%20beta%20TestMatrix
  5. ↑ https://fedorahosted.org/autoqa/browser/hooks/post-koji-build/watch-koji-builds.py
  6. ↑ http://git.fedorahosted.org/git/autoqa.git?a=tree;f=tests/rpmguard
  7. ↑ http://fedoraproject.org/wiki/Template:How_to_debug2
  8. ↑ https://fedorahosted.org/rel-eng/timeline?ticket=on&changeset=on&milestone=on&wiki=on&max=50&daysback=90&format=rss
  9. ↑ http://fedoraproject.org/wiki/Common_F12_bugs
  10. ↑ http://tinyurl.com/l4kma5
  11. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
  12. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-10-20/fedora-meeting.2009-10-20-15.10.log.html
  13. ↑ http://fedoraproject.org/wiki/FUDCon:Toronto_2009
  14. ↑ http://fedoraproject.org/wiki/FUDCon:Toronto_2009#Bus_Travel

Fedora 12 Beta release

Of course, the week's big news was the release of Fedora 12 Beta[1]. This prompted several threads[2] [3] [4] [5] (and more) from enthusiastic testers, with valuable experiences which Adam Williamson encouraged to be turned into bug reports.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00393.html
  2. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00453.html
  3. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00458.html
  4. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00486.html
  5. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00493.html

Confined users Test Day summary

Eduard Benes provided a summary[1] of the SELinux confined users Test Day[2], listing the bug reports resulting from the Test Day and thanking the testers and also Dan Walsh, who had already begun resolving reported bugs.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00488.html
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2009-10-20

Fedora 12 blocker bug review meeting

Adam Williamson provided a recap[1] of the blocker bug review meeting which took place on Friday 2009-10-23, linking to a report[2] 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.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-October/msg00579.html
  2. ↑ http://meetbot.fedoraproject.org/fedora-bugzappers/2009-10-23/fedora-bugzappers.2009-10-23-15.00.html
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=132432"