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

Rohan McGovern rohan.mcgovern at nokia.com
Mon Jan 30 05:24:26 CET 2012


Olivier Goffart said:
> 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.

When this was discussed back when CI was being established on
modularized Qt, the consensus[1] was that the goal should be to keep the
head of all modules working together as much as possible - that's why
people have been discouraged from using anything other than the head of
their dependencies in sync.profile.

[1] which in this case really means "the thing that someone said and no-one
objected to" :)



More information about the Development mailing list