[Development] Suggestion for new CI: "early warning" for qt5.git

[Kent Hansen]

Den 27. jan. 2012 14:07, skrev ext Olivier Goffart:
> On Friday 27 January 2012 09:09:46 Kent Hansen wrote:
> [...]
>> If there is no quick fix, the last resort is to "pin" one or
>> more of the dependencies' to a particular SHA1 (e.g. from the qt5.git
>> submodule) in the sync.profile until the issue has been resolved, then
>> "unpin" it again later.
> Why is that the "last resort"?
> This seems totally normal and was the whole point of modularisation:
> Differents modules can be developped at different speed.

Actually it should be the "first resort". The "right" thing to do is to
1) pin the qtbase sha1 in sync.profile in the modules that you know will 
break because of your qtbase change, and wait for that to get through CI
2) submit your change to qtbase, wait for it to get through CI
3) submit a change to the other modules that unpins the qtbase sha1 and 
adapts to the qtbase change

That avoids any disruption to others. But it's a chore. And you get 
conflicts when several people try to pin/unpin the sha1 at the same time 
(you'd think that wouldn't happen often, but ask Simon ;) ).

> If not, modularisation was just a waste of time and a way to make development
> more difficult.

It does make development more difficult.

Regards,
Kent