>> So anyway, the summary of my thoughts on solving this would be: >> - get 4.x into Gitorious ASAP >> - get the changes into 4.x (can probably be ongoing while the above >> isn't finished, but will be helped) >> - cherry-pick them into Qt 5 (in any way possible) to make sure work >> isn't lost or duplicated, since I assume that your customers will be >> asking about Qt 5 sooner rather than later :) >> >> ...and we're back to working as one big, happy family in Gerrit :) > > Yes, that's the plan, except that we'll get 4.x into gerrit instead of > gitorious ;-) > > Unfortunately moving it into gerrit is not as easy as one might think as > the testing infrastructure is somewhat different between Qt 4.x and Qt 5. > We could move Qt 4.x into gerrit very fast, but would loose the CI on it. > If we want to keep CI, there's some work that needs to happen first. > Sergio and Rohan know the details here. > > Cheers, > Lars
Hi, Basically we need to integrate (or something like it): http://codereview.qt-project.org/9872 http://codereview.qt-project.org/11460 http://codereview.qt-project.org/11462 and we need to make the tests to pass or mark them as insignificant (I already have a patch for this). We have some other options (to start with, improving over time): - No CI et al, direct submit [1] => now - CI with some platforms (linux, windows, mac) enforcing compilation only => a week ? - CI with some platforms (linux, windows, mac) enforcing compilation and autotests = couple of weeks ? - CI with the current platforms in enforcing mode (macosx 10.6, macosx 10.7, winxp msvc2008, win7 msvc2008, win7 msvc2010, linux g++, linux icc) => months ? Cheers, [1]: those who agree then will have to step up and fix the failures when the CI comes back online :) -- Sergio Ahumada Mobile Phones Middleware - Quality Engineering http://wikis.in.nokia.com/QtQualityEngineering _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
