While I agree that this (58133) is a bug, I would not classify it as a bug to 
halt the entire release. It's neither

a regression or a particularly common scenario to run into, I would argue. That 
said, it's a crash, it needs fixing

and I'll fix it.


From: Development <development-bounces+simon.hausmann=qt...@qt-project.org> on 
behalf of Ben Lau <xben...@gmail.com>
Sent: Friday, January 13, 2017 11:38:05 AM
To: Tim Blechmann
Cc: developm...@qt-project.org; releasing@qt-project.org
Subject: Re: [Development] New Qt 5.8 rc snapshot for testing

On 13 January 2017 at 14:15, Tim Blechmann 
<t...@klingt.org<mailto:t...@klingt.org>> wrote:
> All known blockers should be fixed in these packages and we are
> targeting to release Qt 5.8.0 Tue 17^th January if nothing really
> serious found during testing. So please inform me immediately if there
> is some new blocker in the packages.

QTBUG-56163 is the main blocker for me, which prevents me from migrating
to qt-5.8. have already reported it 3 months ago and requested it via
the commercial support.

thanks a lot,

I just submitted QTBUG-58133 on yesterday. It will make applications that use 
QuickFlux crash when passing a signal with QJSValue (isUndefined == true) via a 
C++ class to QML.


Releasing mailing list

Reply via email to