From Fedora Project Wiki

< FWN‎ | Beats

(create 186 qa beat)
(create 187 qa beat)
Line 10: Line 10:
=== Test Days ===
=== Test Days ===


There was no main track Test Day last week. The Fit and Finish project's Test Day track continued with its second Test Day, on power management and suspend/resume<ref>https://fedoraproject.org/wiki/Test_Day:2009-07-21_Fit_and_Finish:Batteries_and_Suspend</ref>. The event was a success, with several testers turning out, many bugs filed, and some fixed during the day or soon afterwards, especially relating to laptops with multiple batteries.
There was no Test Day last week, and No Test Day is currently scheduled for next week. If you would like to propose a main track Test Day for the Fedora 12 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>https://fedorahosted.org/fedora-qa/</ref>.
 
No Test Day is scheduled for next week. If you would like to propose a main track Test Day for the Fedora 12 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>https://fedorahosted.org/fedora-qa/</ref>.


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


The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-07-22. The full log is available<ref>http://fedoraproject.org/wiki/QA/Meetings/20090722</ref>. [[User:Jlaska|James Laska]] reported that he had published a blog post asking people to help with the process of writing Debugging pages<ref>http://jlaska.livejournal.com/5693.html</ref>. [[User:Adamwill|Adam Williamson]] mentioned that he had looked into creating some of the desired pages, but did not know what kind of information was actually required for any of the components concerned. [[User:jkeating|Jesse Keating]] suggested doing an informal interview-style session with maintainers to discover what information is needed, and then having QA take responsibility for turning that information into a finished Wiki page.
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2009-07-27. The full log is available<ref>http://fedoraproject.org/wiki/QA/Meetings/20090727</ref>. [[User:Jlaska|James Laska]] reported that he had contacted the infrastructure team's [[User:Mmcgrath|Mike McGrath]] regarding whether alt.fedoraproject.org has enough resources to make test composes and release candidate builds publicly available. Mike believes it does, so the test composes for Fedora 12 Alpha will be made publicly available as a test. They will be announced to fedora-test-list. A ticket<ref>https://fedorahosted.org/fedora-infrastructure/ticket/1554</ref> is being used to track this.
 
[[User:Jlaska|James Laska]] had created a meeting time matrix<ref>http://fedoraproject.org/wiki/QA_Meeting_Matrix</ref> for the purpose of re-scheduling the QA meeting to make it possible for as many group members as possible to attend. The group agreed that the new meeting day and time should be Mondays at 16:00 UTC, moved from Wednesdays at 16:00 UTC.
 
[[User:Jlaska|James Laska]] noted that a Fedora 12 Alpha blocker bug review meeting was scheduled for Friday 2009-07-24. It was agreed that [[User:Adamwill|Adam Williamson]] would send out an announcement of the meeting, and James would send out a recap after it had finished. [[User:jkeating|Jesse Keating]] mentioned it would be good to do some Rawhide install testing prior to the meeting, but a combination of two significant bugs was preventing almost any Rawhide install from working.


[[User:Jlaska|James Laska]] explained that a test compose for Fedora 12 Alpha was scheduled for 2009-07-29, and [[User:Liam|Liam Li]] had made an announcement requesting help on install testing<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00429.html</ref>. [[User:jkeating|Jesse Keating]] pointed out that it would not be easy for the general public to take part, as the test compose would not be generally distributed. This led to another long discussion about the practicality of distributing time-critical test composes to the public. No definite conclusion was reached, but a tentative agreement was made to look into a system which would allow access to such composes to members of the QA group in FAS.
[[User:Johannbg|Jóhann Guðmundsson]] had not yet been able to contact [[User:Harald|Harald Hoyer]] regarding testing and contingency plans for the Fedora 12 Dracut feature<ref>http://fedoraproject.org/wiki/Features/Dracut</ref>. He will update again at the next meeting.


[[User:Johannbg|Jóhann Guðmundsson]] noted that there were some problems with Dracut, the nash/mkinitrd replacement being introduced as a feature in Fedora 12. It has no implementation plan by which the progress of the feature can be externally measured, and no detailed contingency plan beyond 'revert to mkinitrd'. Jóhann agreed to contact the feature mantainer, [[User:Harald|Harald Hoyer]], to help develop a full test plan and contingency plan.
The group discussed the state of Rawhide in regards to the Alpha test compose that was due the Wednesday following the meeting. [[User:poelstra|John Poelstra]] noted that a bug was currently preventing install images from being generated in Rawhide's daily updates. [[User:jkeating|Jesse Keating]] said a bug should be filed on this and added to the Alpha blocker bug list. [[User:Jlaska|James Laska]] mentioned there were known to be two bugs entirely blocking Rawhide installation from working. [[User:Kparal|Kamil Paral]] mentioned two more bugs which were breaking installation in KVM-based virtual machines. As these are essentially QA's reference platform, the group asked Kamil to add them to the Alpha release blocker list.


[[User:Wwoods|Will Woods]] reported on the progress of the AutoQA project. He has now automated the first four test cases in the Rawhide Acceptance Test Plan<ref>http://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan</ref>, and is now working on automating the installation tests. He noted that separate i386, x86-64 and PowerPC test hosts would be necessary for some tests, and that PPC might be difficult in the absence of the Fedora standard libvirt virtualization framework on that platform. [[User:jkeating|Jesse Keating]] worried that the installation tests may be adding too much complexity to the system, and asked how much faster the process would be if only repository level tests were considered. [[User:Adamwill|Adam Williamson]] pointed out that the full set of repository level tests were the ones that had already been automated. Will promised that they would be updated to send the results somewhere publicly accessible soon.
[[User:Jlaska|James Laska]] noted that a Fedora 12 Alpha blocker bug review meeting was scheduled for Friday 2009-07-31. It was agreed that [[User:poelstra|John Poelstra]] would send out an announcement of the meeting, and [[User:Adamwill|Adam Williamson]] would send out a recap after it had finished.


[[User:sdz|Sebastian Dziallas]] brought up the topic of a Test Day for the Sugar on a Stick project<ref>http://wiki.sugarlabs.org/go/Sugar_on_a_Stick</ref> - essentially for the integration of Sugar with a stock Fedora distribution. It was agreed that the SoaS project would host the Test Day themselves using the SOP created for this purpose<ref>http://fedoraproject.org/wiki/User:Adamwill/Draft_test_day_SOP</ref>. A tentative date of 2009-09-03 was agreed for the test day.
[[User:Wwoods|Will Woods]] reported on the progress of the AutoQA project. He has now automated seven test cases in the Rawhide Acceptance Test Plan<ref>http://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan</ref>, and is working on a script to send out test status emails. He is also working on a blog post and possibly some Wiki documentation regarding the project. [[User:Dpravec|David Pravec]] noted that the latest autotest packages had some problems. [[User:jkeating|Jesse Keating]] would work on fixing those.


The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-07-21. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-07-21/fedora-meeting.2009-07-21-15.02.log.html</ref>. No-one had heard from Brennan Ashton regarding the status of the triage metrics project. [[User:Adamwill|Adam Williamson]] agreed to contact him by email to find out the current status, and ask if he would be interested in having a co-maintainer on the project, in the interest of smoother development.
[[User:jkeating|Jesse Keating]] alerted the group that a Rawhide mass rebuild would be starting during the week, due to the arch change from i586 to i686, new compression format for RPM payloads (XZ), new glibc, and new gcc. He asked everyone to be on the lookout for rebuild-related bugs. [[User:Wwoods|Will Woods]] noted that, after the rpm package itself was rebuilt with an XZ format payload, upgrades from Rawhide installs before the XZ change to current Rawhide would no longer work normally. The best workaround for this issue is to install the updated rpm package from Fedora 11 updates-testing, then update Rawhide as normal. The issue does not affect upgrades from Fedora 11 via yum or anaconda, only upgrades from older to newer Rawhide. [[User:Jlaska|James Laska]] volunteered to submit the issue to [[User:Wtogami|Warren Togami]] for inclusion in the Rawhide Watch blog<ref>http://rawhidewatch.wordpress.com/</ref>.


The group discussed the current draft of the critical path-based triage component list<ref>http://fedoraproject.org/wiki/User:Arxs/CPCL</ref>. There was a general feeling that the list was very long and might contain components that, practically speaking, would not benefit hugely from triage. It also seemed to contain at least some binary (rather than source) package names, while Bugzilla is based on source package names. Niels Haase and [[User:Mcepl|Matej Cepl]] volunteered to adjust the list to use source package names, and break it up into groups for ease of digestion, for further review at next week's meeting.
[[User:Kparal|Kamil Paral]] noted that, at the time of the meeting, the guide to creating live images for test days<ref>http://fedoraproject.org/wiki/QA/Test_Days/Live_Image</ref> had a problem which would cause anyone following it to create a live CD based on Fedora 11, not Rawhide. [[User:Jlaska|James Laska]] thanked him for the report, and promised to look into the problem. (Editor's note: since the time of the meeting, this problem has been fixed, and the guide as it stands works correctly).


[[User:Adamwill|Adam Williamson]] gave an update on the status of the kernel bug triage project. He admitted it had not progressed very far as he had been focussing on anaconda triage. He outlined a plan under which a volunteer would, as a test, triage bugs on one particular component of the kernel, to see if the process could be made to work. [[User:Tk009|Edward Kirk]] thought the proposal a sound one, and Adam agreed to try and put in into practice in the next week.
[[User:Johannbg|Jóhann Guðmundsson]] brought up an old request he had filed for the QA team to have a web page / blog for hosting announcements of QA-related projects, and articles on QA-related topics. The issue was tabled for further discussion as it was not clear exactly what the scope of this page should be, or whether existing Fedora Project pages already sufficiently covered the perceived need. [[User:Adamwill|Adam Williamson]] and [[User:Wwoods|Will Woods]] suggested that a QA team blog aggregator (a Planet) may be another way to achieve this goal.


Finally, the group discussed the 'Bugzilla Semantics' proposal [[User:Adamwill|Adam Williamson]] had made to the mailing list, involving various ways in which the triage process could be tweaked and the use of the NEW and ASSIGNED states changed. Initially discussion was in favour of retaining the status quo, but [[User:jkeating|Jesse Keating]] and [[User:jwboyer|Josh Boyer]] made it clear that the development groups they were involved in used ASSIGNED in a different way to its use by the Bugzappers group, and they would prefer if Bugzappers marked bugs as having been triaged in some other way, so their groups could take advantage of the triage process. It became clear that there would be both benefits and costs involved in changing the triage process. [[User:Adamwill|Adam Williamson]] agreed to send a follow-up email to the mailing list to summarize the current state of the debate, and to see if a consensus could be found on a future path.
The Bugzappers group weekly meeting<ref>http://fedoraproject.org/wiki/BugZappers/Meetings</ref> was held on 2009-07-28. The full log is available<ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-07-28/fedora-meeting.2009-07-28-15.04.log.html</ref>. The group discussed the latest revision of the critical path component list-based expansion of the priority triage packages list<ref>http://fedoraproject.org/wiki/User:Arxs/CPCL</ref>. Since last week, Niels Haase had reduced the size of the list by removing dependencies. The group decided this was a sensible approach given the triaging resources available, and approved merging it into the main priority triage package list<ref>http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref>.  


The next QA weekly meeting will be held on 2009-07-27 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-07-28 at 1500 UTC in #fedora-meeting.
[[User:Adamwill|Adam Williamson]] gave an update on the status of the kernel triage project. [[User:Rjune|Richard June]] had volunteered to start triaging wireless-related kernel bugs, as a test of the viability of the plan. Adam asked him to contact the kernel maintainer with responsibility for wireless, [[User:linville|John Linville]], to notify him of the project and ask for any advice or requests he had, and then to start triaging bugs. Adam would also send a follow-up mail to the group of people interested in the kernel triage project with this current status.


<references/>
Brennan Ashton gave an update on the triage metrics project. His development version of the code was not functional at the time of a meeting due to problems with its database code. He had reverted the public instance of the triage system to the last stable working code, but it had only one day's data available at the time of the meeting. More data would be available shortly after. [[User:Adamwill|Adam Williamson]] asked if, when the development code was ready for production, it would be able to use the existing data, or whether the data would have to be re-generated again. Brennan said that since the development version could use more information than the current stable version, re-generating the data would be faster. Brennan also plans in future to branch the code to use TurboGears 2.0<ref>http://turbogears.org/2.0/</ref>. Adam also asked if Brennan was happy to have co-maintainers on the project, to speed up the work and ensure more reliable availability of maintainers. Brennan said that this was fine, and Adam and Brennan agreed to work together to put out a call for volunteers to help work on the project.


=== F12 Alpha blocker bug review meeting ===
The group discussed again the 'Bugzilla Semantics' proposal [[User:Adamwill|Adam Williamson]] had made to the mailing list. The current feeling on the mailing list and in the meeting seemed to be most in favour of the second option presented in Adam's last email on the topic<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00411.html</ref>. The group agreed to propose option #2 as the way forward on the mailing list, and proceed with it if no serious objections were raised.


[[User:Adamwill|Adam Williamson]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00472.html</ref> the second blocker bug review meeting for Fedora 12, to be held on 2009-07-24, mainly to review blocker bug status for the upcoming Alpha release. Later, [[User:Jlaska|James Laska]] posted a recap of the meeting<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00498.html</ref>.
The next QA weekly meeting will be held on 2009-08-03 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-08-04 at 1500 UTC in #fedora-meeting.


<references/>
<references/>


=== Xfce spin testing ===
=== Benchmarking discussion ===


[[User:maxamillion|Adam Miller]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00391.html</ref> the second test live image with the Xfce desktop, and would appreciate testing and reporting of problems. He noted that the known bugs in Anaconda at the time of the compose may make the image very difficult to install, but it should be usable on most hardware as a live boot.
[[User:Covex|Adam Pribyl]] brought up<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00632.html</ref> Phoronix's benchmarking of Fedora Rawhide in comparison with OpenSUSE, Ubuntu and Mandriva<ref>http://www.phoronix.com/vr.php?view=14045</ref>, suggesting that Fedora's supposed poor performance in these benchmarks should be an issue for concern, in terms of the image of the distribution if nothing else. [[User:Johannbg|Jóhann Guðmundsson]] felt<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00542.html</ref> that benchmarking of a development distribution was fundamentally meaningless. He said ongoing performance monitoring of Rawhide may be useful to development, but would have to properly managed. [[User:frankly3d|Frank Murphy]] agreed with Adam<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00544.html</ref> that, irrespective of the quality of Phoronix's benchmarks, the fact that the site was widely read meant apparent 'poor performance' in Fedora was a problem. As a source of the apparent poor performance, several people pointed out that Rawhide has debugging code enabled that stable releases don't have, and [[DaveJones|Dave Jones]] went into more detail<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00649.html</ref> about some debugging code Fedora enables and which other distributions do not.


<references/>
<references/>


=== KDE QA tester request ===
=== Test Day live image creation ===


[[User:kkofler|Kevin Kofler]] posted a request<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00423.html</ref> for volunteers to help with KDE testing. He noted that the requirements for testers were quite low, and asked interested people to reply to the fedora-kde mailing list or #fedora-kde on IRC. Two people, Aioanei Rares and Marco Crosio, were quick to volunteer, and were accepted as the new KDE testers.
[[User:Kparal|Kamil Paral]] announced<ref>https://www.redhat.com/archives/fedora-test-list/2009-July/msg00549.html</ref> that he had fixed the Test Day live image creation guide<ref>https://fedoraproject.org/wiki/QA/Test_Days/Live_Image</ref> so that images are generated from Rawhide as intended, rather than Fedora 11 as was previously the case.


<references/>
<references/>


=== Bugzilla semantics debate ===
=== Fedora 12 Alpha test compose delay ===


The Bugzilla semantics debate<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00309.html</ref> continued throughout the week, especially following the input from developers at the QA meeting (see above) and the subsequent summary<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00411.html</ref> posted by [[User:Adamwill|Adam Williamson]]. He proposed three options: leaving the current triage process unchanged and encouraging development teams who currently use ASSIGNED to mean a bug has been accepted by a certain developer to use ON_QA instead; changing Bugzappers practice to use a keyword to mark triaged bugs going forward, but leave all existing bugs as they are; or changing Bugzappers practice going forwards and also attempting to 'fix' existing bug reports to use the keyword where appropriate. [[User:jkeating|Jesse Keating]] seemed to favor the second option<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00412.html</ref>, and [[User:poelstra|John Poelstra]] agreed<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00415.html</ref>.
[[User:Liam|Liam Li]] announced<ref>http://www.redhat.com/archives/fedora-test-list/2009-July/msg00656.html</ref> that the test compose for Fedora 12 Alpha had been delayed from 2009-07-29 to 2009-08-06, due to multiple bugs entirely blocking Rawhide installation from working.


<references/>
<references/>

Revision as of 17:07, 3 August 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

There was no Test Day last week, and No Test Day is currently scheduled for next week. If you would like to propose a main track Test Day for the Fedora 12 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[1].

  1. ↑ https://fedorahosted.org/fedora-qa/

Weekly meetings

The QA group weekly meeting[1] was held on 2009-07-27. The full log is available[2]. James Laska reported that he had contacted the infrastructure team's Mike McGrath regarding whether alt.fedoraproject.org has enough resources to make test composes and release candidate builds publicly available. Mike believes it does, so the test composes for Fedora 12 Alpha will be made publicly available as a test. They will be announced to fedora-test-list. A ticket[3] is being used to track this.

Jóhann Guðmundsson had not yet been able to contact Harald Hoyer regarding testing and contingency plans for the Fedora 12 Dracut feature[4]. He will update again at the next meeting.

The group discussed the state of Rawhide in regards to the Alpha test compose that was due the Wednesday following the meeting. John Poelstra noted that a bug was currently preventing install images from being generated in Rawhide's daily updates. Jesse Keating said a bug should be filed on this and added to the Alpha blocker bug list. James Laska mentioned there were known to be two bugs entirely blocking Rawhide installation from working. Kamil Paral mentioned two more bugs which were breaking installation in KVM-based virtual machines. As these are essentially QA's reference platform, the group asked Kamil to add them to the Alpha release blocker list.

James Laska noted that a Fedora 12 Alpha blocker bug review meeting was scheduled for Friday 2009-07-31. It was agreed that John Poelstra would send out an announcement of the meeting, and Adam Williamson would send out a recap after it had finished.

Will Woods reported on the progress of the AutoQA project. He has now automated seven test cases in the Rawhide Acceptance Test Plan[5], and is working on a script to send out test status emails. He is also working on a blog post and possibly some Wiki documentation regarding the project. David Pravec noted that the latest autotest packages had some problems. Jesse Keating would work on fixing those.

Jesse Keating alerted the group that a Rawhide mass rebuild would be starting during the week, due to the arch change from i586 to i686, new compression format for RPM payloads (XZ), new glibc, and new gcc. He asked everyone to be on the lookout for rebuild-related bugs. Will Woods noted that, after the rpm package itself was rebuilt with an XZ format payload, upgrades from Rawhide installs before the XZ change to current Rawhide would no longer work normally. The best workaround for this issue is to install the updated rpm package from Fedora 11 updates-testing, then update Rawhide as normal. The issue does not affect upgrades from Fedora 11 via yum or anaconda, only upgrades from older to newer Rawhide. James Laska volunteered to submit the issue to Warren Togami for inclusion in the Rawhide Watch blog[6].

Kamil Paral noted that, at the time of the meeting, the guide to creating live images for test days[7] had a problem which would cause anyone following it to create a live CD based on Fedora 11, not Rawhide. James Laska thanked him for the report, and promised to look into the problem. (Editor's note: since the time of the meeting, this problem has been fixed, and the guide as it stands works correctly).

Jóhann Guðmundsson brought up an old request he had filed for the QA team to have a web page / blog for hosting announcements of QA-related projects, and articles on QA-related topics. The issue was tabled for further discussion as it was not clear exactly what the scope of this page should be, or whether existing Fedora Project pages already sufficiently covered the perceived need. Adam Williamson and Will Woods suggested that a QA team blog aggregator (a Planet) may be another way to achieve this goal.

The Bugzappers group weekly meeting[8] was held on 2009-07-28. The full log is available[9]. The group discussed the latest revision of the critical path component list-based expansion of the priority triage packages list[10]. Since last week, Niels Haase had reduced the size of the list by removing dependencies. The group decided this was a sensible approach given the triaging resources available, and approved merging it into the main priority triage package list[11].

Adam Williamson gave an update on the status of the kernel triage project. Richard June had volunteered to start triaging wireless-related kernel bugs, as a test of the viability of the plan. Adam asked him to contact the kernel maintainer with responsibility for wireless, John Linville, to notify him of the project and ask for any advice or requests he had, and then to start triaging bugs. Adam would also send a follow-up mail to the group of people interested in the kernel triage project with this current status.

Brennan Ashton gave an update on the triage metrics project. His development version of the code was not functional at the time of a meeting due to problems with its database code. He had reverted the public instance of the triage system to the last stable working code, but it had only one day's data available at the time of the meeting. More data would be available shortly after. Adam Williamson asked if, when the development code was ready for production, it would be able to use the existing data, or whether the data would have to be re-generated again. Brennan said that since the development version could use more information than the current stable version, re-generating the data would be faster. Brennan also plans in future to branch the code to use TurboGears 2.0[12]. Adam also asked if Brennan was happy to have co-maintainers on the project, to speed up the work and ensure more reliable availability of maintainers. Brennan said that this was fine, and Adam and Brennan agreed to work together to put out a call for volunteers to help work on the project.

The group discussed again the 'Bugzilla Semantics' proposal Adam Williamson had made to the mailing list. The current feeling on the mailing list and in the meeting seemed to be most in favour of the second option presented in Adam's last email on the topic[13]. The group agreed to propose option #2 as the way forward on the mailing list, and proceed with it if no serious objections were raised.

The next QA weekly meeting will be held on 2009-08-03 at 1600 UTC in #fedora-meeting, and the next Bugzappers weekly meeting on 2009-08-04 at 1500 UTC in #fedora-meeting.

  1. ↑ http://fedoraproject.org/wiki/QA/Meetings
  2. ↑ http://fedoraproject.org/wiki/QA/Meetings/20090727
  3. ↑ https://fedorahosted.org/fedora-infrastructure/ticket/1554
  4. ↑ http://fedoraproject.org/wiki/Features/Dracut
  5. ↑ http://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan
  6. ↑ http://rawhidewatch.wordpress.com/
  7. ↑ http://fedoraproject.org/wiki/QA/Test_Days/Live_Image
  8. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
  9. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-07-28/fedora-meeting.2009-07-28-15.04.log.html
  10. ↑ http://fedoraproject.org/wiki/User:Arxs/CPCL
  11. ↑ http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
  12. ↑ http://turbogears.org/2.0/
  13. ↑ http://www.redhat.com/archives/fedora-test-list/2009-July/msg00411.html

Benchmarking discussion

Adam Pribyl brought up[1] Phoronix's benchmarking of Fedora Rawhide in comparison with OpenSUSE, Ubuntu and Mandriva[2], suggesting that Fedora's supposed poor performance in these benchmarks should be an issue for concern, in terms of the image of the distribution if nothing else. Jóhann Guðmundsson felt[3] that benchmarking of a development distribution was fundamentally meaningless. He said ongoing performance monitoring of Rawhide may be useful to development, but would have to properly managed. Frank Murphy agreed with Adam[4] that, irrespective of the quality of Phoronix's benchmarks, the fact that the site was widely read meant apparent 'poor performance' in Fedora was a problem. As a source of the apparent poor performance, several people pointed out that Rawhide has debugging code enabled that stable releases don't have, and Dave Jones went into more detail[5] about some debugging code Fedora enables and which other distributions do not.

  1. ↑ http://www.redhat.com/archives/fedora-test-list/2009-July/msg00632.html
  2. ↑ http://www.phoronix.com/vr.php?view=14045
  3. ↑ http://www.redhat.com/archives/fedora-test-list/2009-July/msg00542.html
  4. ↑ http://www.redhat.com/archives/fedora-test-list/2009-July/msg00544.html
  5. ↑ http://www.redhat.com/archives/fedora-test-list/2009-July/msg00649.html

Test Day live image creation

Kamil Paral announced[1] that he had fixed the Test Day live image creation guide[2] so that images are generated from Rawhide as intended, rather than Fedora 11 as was previously the case.

  1. ↑ https://www.redhat.com/archives/fedora-test-list/2009-July/msg00549.html
  2. ↑ https://fedoraproject.org/wiki/QA/Test_Days/Live_Image

Fedora 12 Alpha test compose delay

Liam Li announced[1] that the test compose for Fedora 12 Alpha had been delayed from 2009-07-29 to 2009-08-06, due to multiple bugs entirely blocking Rawhide installation from working.

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