[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: FESCo meeting summary for 2009-06-26

On Fri, Jun 26, 2009 at 5:40 PM, Jesse Keating<jkeating redhat com> 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?


Where would the tests go?  Inside the CVS branch directory for a package?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]