Open, automated, testing of Qt changes

Robin Burchell has continued his series of blog posts on openness within Qt with a piece on community integration testing. His plan consists of a community Qt repository (managed by an integration script) which has Qt's source code overlaid with merge requests; these are built and the unit tests run, with the output being put online. So, after I've described all of the above utopia, what's the current status? Well, I've got a lot of the pieces in place, and now I'm fighting problems with Xvfb causing some of the Qt GUI tests to fail *sometimes*, (even though they don't when I run them manually). Once that is solved, I hope to start adding people's access to integration, and start test-integrating merge requests. Hopefully, all this work will help to accelerate the time it takes to send merge requests back for review if they break something, and ease the burden on getting requests merged in (due to requiring a little less testing). Time will tell. But at least I'm doing my bit. Patches welcome. :) Continuous integration and rapidity in merging patches are key to making large pieces of software work with multiple developers, especially if more developers are going to be available in future. Hopefully Robin's efforts will open up the toolkit and the APIs which are in Maemo and MeeGo's future.