On Fri, 2018-03-02 at 04:40 +0100, Kevin Kofler wrote:
> > I disagree entirely with the above. I think the solution is to gate
> > packages coming into rawhide and hold or reject those that break the
> > compose until they are fixed. I think being proactive is VASTLY better
> > than being reactive. Not breaking something in the first place is much
> > easier to deal with than trying to fix it later.
> And how do you propose doing that? The only reliable way to hold packages 
> that break the compose would be to actually try to run the whole compose 
> process after every package build. That just does not scale.

Then we need to compose faster. This is precisely one of the reasons
why there's quite a lot of work going into exactly that.

"Composes take multiple hours" isn't an immutable law of the universe.
It's a limitation of our compose process, and one we really ought to
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to