On Fri, Jun 26, 2009 at 5:40 PM, Jesse Keating<jkeating@xxxxxxxxxx> wrote: > > Looking even farther in the future to where we have AutoQA functioning, > we can treat critical-path packages differently in the real "rawhide". > Packages outside of critical-path will have autoqa tests done on them in > an informational only way, anything seen wrong will be alerted to the > maintainer and they will fix it if/when they can. Packages within > critical path that have autoqa failures can be prevented from entering > the repo until somebody either fixes it and a build passes the tests, or > a properly authorized account holder forces the build into the repo. Of > course this is just a rough idea how it would work, we have to get > autoqa working first. This all sounds pretty great. Is there more information on AutoQA other than the project here? https://fedorahosted.org/autoqa/ Where would the tests go? Inside the CVS branch directory for a package? -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
