From: development-bounces+mitch.curtis=theqtcompany@qt-project.org
development-bounces+mitch.curtis=theqtcompany@qt-project.org on behalf of
Thiago Macieira thiago.macie...@intel.com
Sent: Friday, 14 August 2015 22:19
To:
Rights have been set. Congratulations.
--
Alex
From: development-bounces+alexander.blasche=theqtcompany@qt-project.org
development-bounces+alexander.blasche=theqtcompany@qt-project.org on
behalf of Milian Wolff milian.wo...@kdab.com
Sent:
I agree that the commit message looks a bit uninformed, given that Qt
should still support WEC (if only 2013+) in Qt 5.7 and beyond. The new
CI has a WEC7 stage, so one would expect that this gets replaced by a
WEC2013 stage at some point in the future.
This assessment is spot on. It's a change
Rights have been set. Congratulations.
--
Alex
From: development-bounces+alexander.blasche=theqtcompany@qt-project.org
development-bounces+alexander.blasche=theqtcompany@qt-project.org on
behalf of Robin Burchell robin...@viroteck.net
Sent:
On Monday 13 July 2015 18:44:40 Thiago Macieira wrote:
On Wednesday 08 July 2015 13:42:12 Thiago Macieira wrote:
The only compiler I currently know that will have problems with this is
the Intel compiler on OS X when using libc++ older than Subversion
r215305. Unfortunately,
Am 17.08.2015 um 11:27 schrieb Blasche Alexander
alexander.blas...@theqtcompany.com:
I agree that the commit message looks a bit uninformed, given that Qt
should still support WEC (if only 2013+) in Qt 5.7 and beyond. The new
CI has a WEC7 stage, so one would expect that this gets
5.6 branching is now complete (*).
anything that integrates to dev now is 5.7 material - as usual, no
cherry-picks.
(*) well, actually, it's, not, because the qtbase downmerge is
non-trivial and needs a review and an integration run, but that's
relevant only for RM, not for the developers.
a
