[Releasing] Qt5.1.1 delayed a bit (was: RE: [Development] Qt5.1.1 known issues)

[Chris Gilbert]

Thank you so much for the update and attempt to get this into 5.1.1.

Of course we don't expect 10.9 to be trouble free or even officially 
supported yet, no problem.

That said, getting the patch in to fix that particular font related 
crash will be a huge win for us in preparing our product for OSX 10.9.
(We can run the thing now, hooray!)

If there are any side-effect issues as a result of the patch then it 
also goes without saying that you should revert it and proceed with the 
5.1.1 release without it.

The rapid response and feedback on this issue is hugely appreciated.

Thanks,
Chris Gilbert
Knald Technologies, LLC

On 8/21/2013 10:51 PM, Heikkinen Jani wrote:
> Hi all!
>
> I discussed with Tuukka this morning and we make the decision to postpone our Qt5.1.1 a bit and try to take fix for QTBUG-31803 in. We agreed it is better to fix this now and get at least something work in 10.9.
> Plan is to make release next Tuesday (27.08.2013). If this fix isn't working or breaks something else then we make our release with existing content but if fix is OK then we release Qt5.1.1 with it.
>
> Br,
> Jani
>
> -----Original Message-----
> From: Turunen Tuukka
> Sent: 21. elokuuta 2013 16:28
> To: Vestbo Tor Arne; Chris Gilbert
> Cc: Heikkinen Jani; development at qt-project.org
> Subject: Re: [Development] Qt5.1.1 known issues
>
>
> Hi,
>
> Regarding not knowing if this patch breaks something else, I think we know
> it quite well when those platforms we have in the CI pass successfully and
> test installer to work in 10.9. Of course we do not have 100% coverage,
> but the risk for this should be relatively low?
>
> Even with this fix in, I would not declare everything to work in 10.9
> before we do have it in the CI (likely in 5.2), but having at least some
> things to work is valuable. Thus I would like to have the fix in 5.1.1,
> unless it does cause big hassle at this point in time.
>
> Yours,
>
> --
>
> Tuukka Turunen
> Director, R&D
> Digia, Qt
>
> Address: Piippukatu 11, 40100 Jyväskylä, FINLAND
> Email: tuukka.turunen at digia.com
> Mobile: + 358 40 7655 800
>
> Qt Website: http://qt.digia.com
> Qt Blog: http://blog.qt.digia.com
> Qt Project: http://www.qt-project.org
>
> ------------------------------------------------------------------
> PRIVACY AND CONFIDENTIALITY NOTICE
> This message and any attachments are intended only for use by the named
> addressee and may contain privileged and/or confidential information. If
> you are not the named addressee you should not disseminate, copy or take
> any action in reliance on it. If you have received this message in error,
> please contact the sender immediately and delete the message and any
> attachments accompanying it. Digia Plc does not accept liability for any
> corruption, interception, amendment, tampering or viruses occurring to
> this message.
> ------------------------------------------------------------------
>
>
>
>
>
>
> On 21.8.2013 16.15, "Tor Arne Vestbø" <tor.arne.vestbo at digia.com> wrote:
>
>> This should fix it (tested built on 10.7 and deployed on 10.8 and 10.9):
>>
>> https://codereview.qt-project.org/#change,63483
>>
>> tor arne
>>
>> On 8/21/13 14:15 , Chris Gilbert wrote:
>>> Thanks for the follow up!
>>>
>>> If there is no existing, tested fix I understand completely, no problem.
>>>
>>> I was under the impression that the issue had been resolved some weeks
>>> ago - I recall seeing a couple of patches regarding the font system that
>>> looked related.
>>>
>>> (I popped into IRC a while back and was directed to them for testing
>>> when I asked about the issue)
>>>
>>> Thanks!
>>> Chris Gilbert
>>>
>>>
>>>
>>> On Aug 21, 2013, at 4:25, Heikkinen Jani <Jani.Heikkinen at digia.com>
>>> wrote:
>>>
>>>> There isn't fix for that available at the moment.  And as said, 10.9
>>>> isn't supported yet. We discussed about this with several persons and
>>>> agreed this isn't blocking the release. We don't have 10.9 in the CI
>>>> yet so we cannot know what else is broken so that's why it doesn't make
>>>> sense to delay to release because of this, sorry about that.
>>>>
>>>> Br,
>>>> Jani
>>>>
>>>> -----Original Message-----
>>>> From: development-bounces+jani.heikkinen=digia.com at qt-project.org
>>>> [mailto:development-bounces+jani.heikkinen=digia.com at qt-project.org] On
>>>> Behalf Of Chris Gilbert
>>>> Sent: 21. elokuuta 2013 5:11
>>>> To: development at qt-project.org
>>>> Subject: Re: [Development] Qt5.1.1 known issues
>>>>
>>>> Is there any chance that the patch currently in 5.1.2 for this bug can
>>>> be put into 5.1.1?
>>>> https://bugreports.qt-project.org/browse/QTBUG-31803
>>>>
>>>> QT is largely non-operable on OSX 10.9 currently. Having this in 5.1.1
>>>> would be a huge benefit to those of us trying to support 10.9 out of
>>>> the
>>>> gate.
>>>>
>>>> Thanks,
>>>> Chris Gilbert
>>>> Knald Technologies, LLC
>>>>
>>>> On 8/20/2013 1:12 PM, Petko Ditchev wrote:
>>>>> https://bugreports.qt-project.org/browse/QTBUG-33093 . Just saw this
>>>>> in
>>>>> my app - can anyone confirm ?
>>>>>
>>>>> Petko
>>>>> _______________________________________________
>>>>> Development mailing list
>>>>> Development at qt-project.org
>>>>> http://lists.qt-project.org/mailman/listinfo/development
>>>> _______________________________________________
>>>> Development mailing list
>>>> Development at qt-project.org
>>>> http://lists.qt-project.org/mailman/listinfo/development
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development