08:08:25 <flock-b286> #startmeeting
08:08:25 <zodbot> Meeting started Wed Aug  6 08:08:25 2014 UTC.  The chair is flock-b286. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:08:25 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
08:08:32 <flock-b286> #meetingname Fedora QA - You are important
08:08:32 <zodbot> The meeting name has been set to 'fedora_qa_-_you_are_important'
08:09:16 <flock-b286> #meetingtopic Fedora QA
08:09:26 <flock-b286> #topic Why
08:09:56 <flock-b286> improve performance; find bugs; etc. Improve products!
08:10:50 <flock-b286> Participating in Fedora Test Days even if you don't know much about the products in question, contributions are possible
08:11:02 <flock-b286> #topic Fedora QA overview
08:11:31 <flock-b286> Rawhide, update and release testing; automated and validation testing; test plan/case creation; filing bugs; running tests; weekly meetings; build test strategizing
08:13:12 <flock-b286> #topic rawhide pkg testing
08:14:06 <flock-b286> rawhide is not stable; test only on test machines, not production; anything odd should be reported; earlier the better
08:14:13 <flock-b286> #topic branching point
08:14:28 <flock-b286> F21 branched off of Rawhide recently
08:15:31 <flock-b286> rawhide is rolling; branch point is when the 'next release' is branched out (f21); to start testing current release under dvelopment; just disable rawhide repos
08:16:07 <flock-b286> Rawhide Report provides detailed build info about status; rawhide blog (awilliamson) reports status
08:16:27 <flock-b286> #topic update testing
08:17:06 <flock-b286> use Bodhi provides nice web-ui where you can find your update packages where you can see what was fixed, etc
08:17:27 <flock-b286> If it works; give +1 Karma to developer
08:18:08 <flock-b286> discussions about test results can happen on mailing list, IRC etc
08:18:28 <flock-b286> Q: how does one get karma to give? A: fas account
08:18:43 <flock-b286> updated packages for testing; enable updates-testing reposity
08:19:08 <flock-b286> update test report (daily) shows details about updates packages needing testing
08:19:16 <flock-b286> #topic test plans/cases
08:19:47 <flock-b286> more help needed! if you have a package, contibute tests, please
08:20:03 <flock-b286> Just make sure to follow Fedora Test Plan/Case "format' standard
08:20:19 <flock-b286> all available via fedoraproject.org/wiki
08:20:53 <flock-b286> #topic bugs
08:21:09 <flock-b286> tracking tool for fedora: bugzilla.redhat.com
08:21:43 <flock-b286> github.com/atodorov/qe_metrics for tracking bug filed
08:22:37 <flock-b286> ABRT (automated bug reporting tool) which can be setup on your test machine; configurable so that stacktraces can be submitted automatically based on certain events
08:23:09 <flock-b286> when opening bugs, follow guidelines. Search for Bugzilla Etiquette for more info
08:24:49 <flock-b286> tldr; make sure YOU can reproduce the issue if asked to based on your report... otherwise how would the developer do it...
08:24:56 <flock-b286> #topic Test Days
08:25:08 <flock-b286> aka, fedora qa Party!
08:25:26 <flock-b286> run between alpha <-> GA
08:25:33 <flock-b286> irc #fedora-test-day
08:25:53 <flock-b286> anyone can propose/host a test day; just add info to the wiki
08:28:12 <flock-b286> promote promote promote! and make sure to schedule it according to target audience's availability
08:28:38 <flock-b286> remark from audience (joe): add info to Fedora Magazine
08:29:25 <flock-b286> check the fedoraproject calendar for upcoming Test Day events
08:29:33 <flock-b286> #topic
08:29:37 <flock-b286> #topic how to contribute
08:30:09 <flock-b286> Create FAS account; subscribe to test mailing list = test@lists.fedoraproject.org; create test cases/plans for rpms; test pkgs in Bodhi; Participate and Organize Test Days
08:30:27 <flock-b286> contributions are welcomed and desired even from casual users
08:31:36 <flock-b286> #topic getting help
08:31:49 <flock-b286> Fedora wiki pages; ... slides will be available
08:32:04 <flock-b286> #topic Q&A
08:32:30 <flock-b286> Q: as maintainer, how to write automated tests for my pkg? and what's status of beaker in fedora
08:33:30 <flock-b286> A: autoqa and taskton is there; beaker is also there (can setup your own lab and automated test executions);
08:34:35 <flock-b286> A: beaker is not available to public audience; beaker is there but doesn't really work; taskatron is where to go; tim flink is the contact; taskatron is replacing autoqa; but not currently available either for general audience for running third-party tests
08:35:13 <flock-b286> right now, only manual test cases can be run (via bohdi)
08:35:32 <flock-b286> Q: how would you describe current state of Fedora QA
08:36:10 <flock-b286> A: good question; full-time team is in place. but many pkgs and not enough of us... getting better, but lots of room to improve
08:36:32 <flock-b286> Q: is there some sort of organized triage of incoming bugs or is it up to developers
08:37:29 <flock-b286> A: used to have a triage committee; now it's not working; short of people. Most of developers are handling this. Most bugs are zombies and we definitely need to recommit to this.
08:38:12 <flock-b286> Q: why is bug zappers in such bad shape;
08:38:51 <flock-b286> A: it's surprisingly hard to triage bugs; often need specialized knowledge; gets annoying when people do the work but then later devs don't do anything anyway... not immediate reward.
08:40:30 <flock-b286> Q: past few releases, quality of initial alpha releases has gone up; what are the remaining bottlenecks for further improvements
08:40:55 <flock-b286> A: lack of testers; spinning too many plates at once; fast pace of release cycles
08:42:12 <flock-b286> we need more people testing products; and testing specialized services/packages. and of course, developers...
08:44:11 <flock-b286> Idea; what about creating a Bug Triage day (ala test day)
08:44:48 <flock-b286> Q: any room at Flock 2014 for doing bug zapper/triage hackfest?
08:45:00 <flock-b286> #endmeeting