QualityAssurance
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
Test Days
Last week's Test Day[1] was on webcams. We had a great turnout, with many users testing all sorts of different cameras, so thanks to everyone who tested. Most cameras were reported to work well, but we did identify a few models which did not, and Hans de Goede will be working to improve support for those. Thanks to Hans for helping to organize and look after the event.
Next week's Test Day[2] will be on Fedora 13 changes to disk management, via the udisks (previously DeviceKit-disks) backend and the Palimpsest front end[3]. The major new features are better support for LVMs, support for multipath connections (a system with multiple connections to the same drive, common with enterprise storage systems) and support for remote access, allowing you to inspect the disks on one system from another with Palimpsest. As always, we'll be working to make testing as easy as possible, and most testing should be possible from a live environment. The Test Day will run all day on Thursday 2010-03-18 in the #fedora-test-day IRC channel.
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].
Weekly meetings
No QA group weekly meeting was held on 2010-03-08 as James Laska was unavailable and there were no pressing items needing discussion.
The Bugzappers group weekly meeting[1] was held on 2010-03-09. The full log is available[2]. Matej Cepl confirmed that he is an administrator of the Fedorahosted triage space[3], and that XML-RPC access to the space is now working again.
Adam Williamson provided a recap of Brennan Ashton's work on triage statistics[4], and on his current plan[5] to develop this within the Fedora Community[6] group.
Adam Williamson and John Poelstra discussed the planned rebase of bugs to Fedora 13, in regards to some questions[7] raised by Till Maas on the development mailing list. They confirmed that each specific rebase does not need approval by FESCo, and could not see how Till's proposed refinement of the rebase query would be an improvement.
Adam Williamson reported that he had updated the bug workflow Wiki page[8] to reflect the new No Frozen Rawhide process. He noted that it had been slightly cumbersome to rewrite and welcomed reviews of the changes. Christopher Beland volunteered to update the Rawhide page[9] similarly.
The next QA weekly meeting will be held on 2010-03-15 at 1600 UTC in #fedora-meeting. The next Bugzappers weekly meeting will be held on 2010-03-16 at 1500 UTC in #fedora-meeting.
- ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2010-03-09/fedora-meeting.2010-03-09-15.04.log.html
- ↑ http://fedorahosted.org/triage/
- ↑ http://lists.fedoraproject.org/pipermail/infrastructure/2009-April/006513.html
- ↑ http://lists.fedoraproject.org/pipermail/infrastructure/2010-February/008373.html
- ↑ http://admin.fedoraproject.org/community/
- ↑ http://lists.fedoraproject.org/pipermail/devel/2010-March/132390.html
- ↑ http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
- ↑ http://fedoraproject.org/wiki/Releases/Rawhide
Fedora 13 Alpha and Beta
Jesse Keating announced[1] the release of Fedora 13 Alpha on 2010-03-09. The first blocker bug review meeting for Fedora 13 Beta was held on 2010-03-12[2], where all Beta blocker candidate bugs were reviewed and some Fedora 13 blocker candidates upgraded to Beta blocker status.
Package update policy
Kamil Paral posted[1] a proposed draft[2] of a package update policy, driven mostly by the need for a framework for the integration of AutoQA tests. Kamil's policy was eventually discussed at the FESCo meeting[3] which decided to move forward with Bill Nottingham's proposal focused on the requirements for updates to be published. Kamil planned to work with Bill to ensure his proposal would cover the important areas of Kamil's draft.