19:09:52 <SMParrish> #startmeeting 19:09:52 <zodbot> Meeting started Sat Dec 5 19:09:52 2009 UTC. The chair is SMParrish. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:09:52 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:10:27 <SMParrish> #topic Planned Testing 19:11:14 <SMParrish> There are 2 types of planned testing. Test days & Pre-release/Final release testing 19:11:36 <SMParrish> Test days are communal, focused and suported by IRC & Wiki 19:11:57 <SMParrish> Can be organized by anyone, not just Fedora QA 19:12:26 <SMParrish> #link http://fedoraproject.org/wiki/QA/Test_Days 19:13:20 <SMParrish> Pre-release / Final release testing are composed of Image validation and an install test matrix 19:13:51 <SMParrish> If you discover a bug that you think should block the release of Fedora you can use the keyword Blocker 19:14:16 <SMParrish> There is a blocker review process to determine if bug is an actual blocker 19:15:14 <SMParrish> Anyone can mark a bug as a blocker, just need a bugzilla account 19:15:55 <SMParrish> #topic AutoQA 19:16:33 <SMParrish> There is an AutoQA talk by Will Woods scheduled for 1600 in Room 2 19:17:59 <SMParrish> This is a framework for automating testing of Fedora packages. You can develop your own test cases and triggers 19:18:21 <SMParrish> This a great hacker project. System is written in Python 19:18:33 <SMParrish> #topic BugZappers 19:18:57 <SMParrish> BagZappers are responsible for performing triage on bugs reported against Fedora Packagers 19:19:17 <SMParrish> in the past package maintainers had to triage the bugs themselves 19:20:06 <SMParrish> Now a group of volunteers go over every bug report to ensure that all the required information needed is in the report 19:20:58 <SMParrish> The Bugzappers act as a liason between the maintainers and the reporters, this gives the maintainer more time to actually work on fixes 19:22:12 <SMParrish> When a bug contains everything the maintainer needs it is flagged as Triaged. This alerts the maintainer that a bug report is ready and contains all the info they need to begin their work 19:23:10 <SMParrish> #link http://fedoraproject.org/wiki/BugZappers 19:24:02 <SMParrish> BugZappers meet every Tuesday at 1500 UTC on #fedora-meeting. We can be found at other times in #fedora-bugzappers 19:24:25 <SMParrish> Very easy ramp to contribute. Its a great place to start. Join us 19:25:16 <SMParrish> Other resources 19:25:30 <SMParrish> http://fedoraproject.org/wiki/QA 19:25:40 <SMParrish> http://fedoraproject.org/wiki/BugZappers 19:26:03 <SMParrish> #link http://fedoraproject.org/wiki/BugsAndFeatureRequests 19:26:11 <SMParrish> #link http://fedoraproject.org/wiki/BugZappers 19:26:19 <SMParrish> #link http://fedoraproject.org/wiki/QA 19:26:34 <SMParrish> #link http://fedoraproject.org/wiki/AutoQA 19:26:53 <SMParrish> #link http://fedoraproject.org/wiki/QA/Test_Days 19:27:11 <SMParrish> #link http://fedoraproject.org/wiki/Category:Test_Plans 19:30:56 <SMParrish> About 55-60% percent of bugs filed against Fedora packages are eventually resolved 19:32:27 <SMParrish> You can watch for upcomming updates by using http://bodhi.fedoraproject.org and monitoring updates-testing 19:33:21 <SMParrish> Thru Bodhi you can comment on a package and vote it either up or down for getting pushed out to the stable repos 19:33:50 <SMParrish> There is a mailing list for Fedora QA fedora-test-list you can subscribe at 19:34:11 <SMParrish> #link http://lists.fedoraproject.org 19:35:21 <SMParrish> important IRC Channels 19:35:21 <SMParrish> #fedora-qa 19:35:21 <SMParrish> #fedora-bugzappers 19:35:24 <SMParrish> #fedora-test-days 19:37:33 <SMParrish> #link alt.fedoraproject.org/pub/alt/nightly-composes 19:38:08 <SMParrish> this will give you access to the latest rawhide version of the Fedora LiveCDs 19:39:42 <SMParrish> images are available for i386 and x86_64 19:40:01 <SMParrish> #endmeeting