[Development] CI configuration changes

[Rutledge Shawn]

On 21 Jan 2015, at 08:19, Turunen Tuukka <tuukka.turunen at theqtcompany.com> wrote:

> 
> On 20/01/15 21:44, "Thiago Macieira" <thiago.macieira at intel.com> wrote:
> 
>> On Tuesday 20 January 2015 19:21:04 Sarajärvi Tony wrote:
>>>> What's your timeline for this?
>>> 
>>> If I don't get any objections here, I could start the work immediately.
>>> Goal
>>> is to do it right away, so that we have time to verify the platforms
>>> before
>>> 5.5 feature freeze.
>>>> If you're looking at this for before the Qt 5.5
>>>> feature freeze, OS X 10.7 will break and will be effectively
>>> unsupported
>>>> for 5.5 because I won't bother fixing forkfd for it.
>>> 
>>> My understanding is that OS X 10.7 is allowed to break in 5.5.
>> 
>> Usually we give people a one version notice... So we shouldn't allow it
>> to 
>> break in 5.5, but announce that support drops in 5.6.
> 
> OS X 10.7 has been listed as Tier 2 already for Qt 5.4:
> http://doc.qt.io/qt-5/supported-platforms.html
> 
> That said, we should of course carefully consider whether or not it is
> supported with Qt 5.5.

Maybe we should leave it in CI for the 5.5 timeframe.  What would we have to give up to do that?

This is an example of why I’d like our CI system to be transformed into a distributed one: it should be possible for anyone to add machines to the pool.  Even if some of them are non-binding… e.g. a contributed machine would only be able to do +1/-1 on a patch, as a warning that a certain patch will break a tier 2 platform.  There are many such platforms which we aren’t testing.