On Thursday 13 October 2011 12:22:39 Simon Hausmann wrote: > Hey, > > There are plenty of source incompatible changes going into the Qt 5 modules. > This can make development of depending modules difficult. > > I recall that the KDE 4 development cycle had similar issues, and I have > vague memories of this being mitigated with a simple procedure: Source > incompatible changes were pushed only once a week (on Mondays?). > > Would it make sense to do the same for Qt 5 development?
I think the situation is different now than with KDE4: use of git instead of svn, Qt being more modular, CI system, ... With the CI system it is almost impossible to know in advance when a change will get integrated. In the implementation i know (from few month ago), the tests are only run when one clicks "Integrates", which means the source incompatible changes will only be run on monday and are likely to fail because changes being batched up. (Source incompatible changes are usually dependences for others changes that also have to wait) Not to count the problem with conflicts that will happen Hopefully now, there is not many source incompatible changes. (+1 for review on the list, i think it was part of lars's statement that all source incompatible changes must have proper review) Anyway, the goal of the modularisation was that module would envolve separately. Then, if it is a problem for modules, the solution is that modules depends on a sha1 of qtbase from the previous monday. (Only update qtbase every monday. in qt5.git) And this also help with binary compatibility. _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
