(create fwn 252 qa beat) |
(create fwn 256 qa beat) |
||
| Line 8: | Line 8: | ||
<references/> | <references/> | ||
=== | === Test Days === | ||
The Fedora 15 Test Day calendar is starting to take shape, and you can see what events are planned so far on the Wiki page<ref>http://fedoraproject.org/wiki/QA/Fedora_15_test_days</ref>. The first Test Day slot is 2011-01-27. If you would like to propose a main track Test Day for the Fedora 15 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac<ref>http://fedorahosted.org/fedora-qa/</ref>. | |||
=== Hands-on Bugzapping session at FOSS.in === | |||
=== | |||
[[User:Siddhesh|Siddhesh Poyarekar]] announced his intention<ref>http://lists.fedoraproject.org/pipermail/test/2010-December/095926.html</ref> to run a hands-on introduction to bug triage at FOSS.in<ref>http://foss.in/</ref>, a major F/OSS event in India. The event will take place during the Fedora mini-conference on 2010-12-16. [[User:Sundaram|Rahul Sundaram]] will help him with this effort<ref>http://lists.fedoraproject.org/pipermail/test/2010-December/095927.html</ref>. | |||
<references/> | <references/> | ||
=== | === Bugzappers meeting time change === | ||
At the first Bugzappers meeting for a while<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-12-07/fedora-meeting.2010-12-07-21.04.html</ref>, the group agreed that in the future, meetings would be held bi-weekly from 2011-01-11, at 21:00 UTC. | |||
<references/> | <references/> | ||
=== | === Bugzappers component prioritization === | ||
Also at the Bugzappers meeting, the group agreed it would be beneficial to look at which of the critical path components (the packages Bugzappers aim to work on with the most priority) are actually very commonly subject to bug reports which require triage, and prioritize those components, listing them on the components page<ref>http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers</ref> in a separate table, to make it easier for new triagers to pick a component which will be practical to work on. Andrew Roth volunteered to work on this. | |||
<references/> | <references/> | ||
Revision as of 18:01, 15 December 2010
QualityAssurance
In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].
Contributing Writer: Adam Williamson
Test Days
The Fedora 15 Test Day calendar is starting to take shape, and you can see what events are planned so far on the Wiki page[1]. The first Test Day slot is 2011-01-27. If you would like to propose a main track Test Day for the Fedora 15 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[2].
Hands-on Bugzapping session at FOSS.in
Siddhesh Poyarekar announced his intention[3] to run a hands-on introduction to bug triage at FOSS.in[4], a major F/OSS event in India. The event will take place during the Fedora mini-conference on 2010-12-16. Rahul Sundaram will help him with this effort[5].
Bugzappers meeting time change
At the first Bugzappers meeting for a while[1], the group agreed that in the future, meetings would be held bi-weekly from 2011-01-11, at 21:00 UTC.
Bugzappers component prioritization
Also at the Bugzappers meeting, the group agreed it would be beneficial to look at which of the critical path components (the packages Bugzappers aim to work on with the most priority) are actually very commonly subject to bug reports which require triage, and prioritize those components, listing them on the components page[1] in a separate table, to make it easier for new triagers to pick a component which will be practical to work on. Andrew Roth volunteered to work on this.