On Mon, 2011-01-24 at 16:52 +0100, Kevin Kofler wrote: > Simo Sorce wrote: > > We can easily test for rpath, > > But who does it on all packages regularly? AutoQA is still vaporware.
Because you haven't taken the time to familiarize yourself with a project doesn't make it vaporware. AutoQA [1] works, it's running tests against *every* koji-built package, proposed bodhi updates and any repodata/install_image changes. Unfortunately, there is no out-of-the-box solution that does everything the Fedora project needs. As a result, a lot of ground work has been required. You may have seen related discussion in QA meetings or on the planet. The current focus is automating the package update acceptance test plan [2], which attempts to address the approved update criteria [3]. If you have specific concerns about AutoQA, or are able to invest time/ideas, I'll be happy to discuss with you. There is an active development discussion list (autoqa-de...@lists.fedorahosted.org), and we're always in need of volunteers to help work down the mountain of outstanding tasks. Otherwise, please don't discredit the hard work of engineers and volunteers who invested their time by calling it vaporware. Thanks, James [1] https://fedoraproject.org/wiki/AutoQA [2] https://fedoraproject.org/wiki/QA:Package_Update_Acceptance_Test_Plan [3] https://fedoraproject.org/wiki/Package_update_acceptance_criteria
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
