[Development] Integration of qt5.git

[Alan Alpert]

On Fri, Nov 29, 2013 at 12:50 PM, André Pönitz
<andre.poenitz at mathematik.tu-chemnitz.de> wrote:
> On Fri, Nov 29, 2013 at 05:16:31PM +0000, Gladhorn Frederik wrote:
>> Hello all,
>>[...]
>>
>> Since we lose the test runs for all modules at the same time I'd like to
>> have a second and new job in Jenkins that runs nightly and builds and
>> runs all tests of all modules (according to qt5.git state). This job
>> doesn't mean anything for the integration and doesn't block but simply
>> sends mail to this list whenever any test fails.  I actually expect it to
>> fail regularily since we have quite a few unstable unit tests that every
>> once in a while fail. I hope that this approach gives actually more
>> visibility to failing auto tests than what we currently have.

Regular emails from a bot broadcast to devel when the break could be
anywhere in qt5.git's submodules... I'm not sure that will be
effective for getting it fixed. Despite the recent marketing blitz,
people only really step up to fix someone else's tests when it's
blocking their integration.

Is it possible to have a more targeted approach, like it emailing the
relevant maintainer(s) instead (or a QA team, if we still have one)?

>[...]
> Since the main use of qt5.git is to _release_ stuff, its setup and
> policies should cater to exactly that need first. If it works for other
> use cases that's fine, but in no way essential.

I concur. The only time I hear about qt5.git is around release time
and I'd rather not hear about it at all (that is to say, the process
should work so smoothly and well that it never comes up ;) ). Do what
you feel is necessary.

--
Alan Alpert