Responsibility for rebuilding dependent components, was: F-16 Branched report: 20110920 changes

Adam Williamson awilliam at
Thu Oct 6 19:50:24 UTC 2011

On Tue, 2011-10-04 at 09:07 -0700, Adam Williamson wrote:
> On Fri, 2011-09-23 at 16:31 -0400, Doug Ledford wrote:
> > ----- Original Message -----
> > > The setup inside Red Hat cannot be (directly) copied outside at this
> > > time.  Instead the autoQA project was started to re-create it as an
> > > open source project.  That's where effort should continue.
> > 
> > Am I right in saying that AutoQA is basically mired in the muck and going nowhere at the moment?
> "at the moment", yes, but that's with a very narrow scope of "at the
> moment" - i.e. for the last few weeks. I don't want Kamil's email to
> give the impression that AutoQA has been going nowhere for months,
> because that certainly isn't the case. Work has slowed down in the last
> few weeks because Fedora 16 Beta testing was extremely problematic and
> sucked up most of the AutoQA manpower, and QA is anyway undermanned
> (from a Red Hat paid staff viewpoint) ATM. It should speed up again to a
> lesser degree now, and to a greater degree when Final is done and we
> have a couple more bodies in place.
> I think adding some more rpmdiff-type tests to current AutoQA wouldn't
> actually be a huge stretch, but I'd bow to Tim or Kamil on the detail
> front there.

Not to bash the thing to death, but Kamil did a presentation on AutoQA
at FUDCon Milan, the slides are well worth reading:

they provide a pretty good potted explanation of what the big priorities
in AutoQA development are right now, why they're important, why AutoQA
can't really accept outside test contributions right now (and what needs
fixing before it can), and in general why AutoQA is kind of in 'swan
mode' at the moment - it looks like nothing much is going on above the
waterline, but below the surface the legs are pumping away madly :)
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | adamwfedora

More information about the devel mailing list