On Mon, 2011-01-24 at 16:52 +-0100, Kevin Kofler wrote: +AD4 Simo Sorce wrote: +AD4 +AD4 We can easily test for rpath, +AD4 +AD4 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 +AFs-1+AF0 works, it's running tests against +ACo-every+ACo koji-built package, proposed bodhi updates and any repodata/install+AF8-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 +AFs-2+AF0, which attempts to address the approved update criteria +AFs-3+AF0. 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-devel+AEA-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 +AFs-1+AF0 https://fedoraproject.org/wiki/AutoQA +AFs-2+AF0 https://fedoraproject.org/wiki/QA:Package+AF8-Update+AF8-Acceptance+AF8-Test+AF8-Plan +AFs-3+AF0 https://fedoraproject.org/wiki/Package+AF8-update+AF8-acceptance+AF8-criteria
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
