On Thursday, January 26, 2012 09:41:45 Jedrzej Nowacki wrote: > > > > Lets take a look at the current numbers:
Can you post numbers for QtBase only instead? That's the most active, the most strictly reviewed (more iterations), and the repo where breakage has the most impact. > > Could we get there? Perhaps. But we would need quite a few compromising > > shortcuts to get there, I think :) > > You are assuming that we need to test every patchest which would be > nice, but it is not necessary. > > We do not need to test every platform, only the fastest one. Hear, hear! I wonder if it's possible for the CI system to maintain and clone a working master build which patches could be applied to and build incrementally? (an un-clean build) > Currently, there is no way to test properly difficult patches without > staging them. Agreed. Quite annoying. Getting approval scores in reviews is only the beginning because CI still has to be started at that point. Thanks, -- Stephen Kelly <stephen.ke...@kdab.com> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
