On Thu, 2012-02-16 at 08:46 -0500, Vincent L. wrote: > Thanks for the stats and information. > > How big is the gap in testing. > > Is there a significant amount of package releases etc walked back > because after they passed minimum time in QA and were published it > turned out they were broken ? Ie. percent wise or some other metric > or in the absence of that a gut assessment. No, we almost never revert updates. I can't recall a single instance of it happening recently. When an update breaks something the packager usually simply ships a quick fix as a subsequent update. > Are certain areas in more need of focus than others due to criticality > and lack of testing/testers ? If so what areas are those ? The packages we'd like most to have test plans are those on the critical path - https://fedoraproject.org/wiki/Critical_path_package , http://kojipkgs.fedoraproject.org/mash/rawhide-20120101/logs/critpath.txt . > Wanting to get a handle on things around here so I can understand > where I can be most effective in helping out. I want to look into the > automated qa testing via this link > https://fedoraproject.org/wiki/AutoQA Great. AutoQA has its own mailing list, and the wiki should have lots of helpful info and contacts for getting started. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
