Re: [Development] Qt LTS & C++11 plans
On Monday 17 August 2015 23:25:05 Jake Petroules wrote: > I haven't a clue why people would bother using old OS X platforms for > development, *especially* now that they don't charge for it. Plus I think > submitting to app stores requires the latest Xcode anyways so there's > another point against it. Right. In the past, the thinking was that people wouldn't upgrade because it would require them to pay for it. That reason is now gone. They may still complain if the newer versions of OS X no longer run on some older hardware. But isn't it true that all 64-bit capable Intel Mac can run the latest OS X? Or is there any hardware that would have upgraded to 10.8 but not further? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt LTS & C++11 plans
> On Aug 17, 2015, at 10:46 PM, Thiago Macieira > wrote: > > 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, _LIBCPP_VERSION has been at value 1101 since way >>> before that change. To restore functionality, I will revert >>> 1b961e8b5d508d054e31c0050f27891606714393 after 5.6 branches off from dev. >> >> Upon further investigation, it turns out that ICC has worked around the >> libc++ problem since version 15.0 by providing its own std::atomic >> implementation when __clang__ is defined (probably a mistake and should >> have been a check for _LIBCPP_VERSION). > > Looks like std::atomic that came with the latest XCode that still runs on OS > X > 10.8 is also broken with Clang. > > Choices: > 1) drop the ability to build Qt and applications using an old XCode > 2) keep qatomic_x86.h for OS X. > > So, Mac people: is it ok to drop OS X 10.8 as a *build* platform? This should > not affect using it as a target. > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development I haven't a clue why people would bother using old OS X platforms for development, *especially* now that they don't charge for it. Plus I think submitting to app stores requires the latest Xcode anyways so there's another point against it. -- Jake Petroules - jake.petroules at petroules.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt LTS & C++11 plans
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, _LIBCPP_VERSION has been at value 1101 since way > > before that change. To restore functionality, I will revert > > 1b961e8b5d508d054e31c0050f27891606714393 after 5.6 branches off from dev. > > Upon further investigation, it turns out that ICC has worked around the > libc++ problem since version 15.0 by providing its own std::atomic > implementation when __clang__ is defined (probably a mistake and should > have been a check for _LIBCPP_VERSION). Looks like std::atomic that came with the latest XCode that still runs on OS X 10.8 is also broken with Clang. Choices: 1) drop the ability to build Qt and applications using an old XCode 2) keep qatomic_x86.h for OS X. So, Mac people: is it ok to drop OS X 10.8 as a *build* platform? This should not affect using it as a target. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] HEADS-UP: Qt 5.6 feature freeze and branching coming
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 mini-post-mortem already: as every single time so far, something went wrong with the supermodule (this time it was bad versioning in canvas3d, which repeatedly threw off the branch/merge script). for a smooth process, it's really essential that the supermodule and all submodules are in a consistent state *before* the branching *starts*. take that as a reminder that if you are adding a new module to the supermodule, it's your responsibility to verify that the module is actually built in a sane way within the new context. On Fri, Aug 07, 2015 at 10:06:33AM +, Heikkinen Jani wrote: > Hi all, > > > As far as I know there shouldn't be anything preventing us to have FF & start > branching on Monday 10th Aug as planned. There is still work to do in new CI > side but that shouldn't prevent us to proceed with FF. > > > Qt5.git update isn't working in 'dev' yet but after discussion with Lars & > others internally we agreed it isn't a blocker for FF & branching. Of course > it needs to be working before alpha release (which is planned to happen 8th > September). > > > So if nothing new turns out later today/during the weekend Qt 5.6 feature > freeze is on Monday morning and we will start branching. We will use soft > branching like earlier so there should be enough time to finalize ongoing > changes for Qt 5.6 in 'dev' & start using '5.6' branch for Qt 5.6 > development. And like earlier final downmerge from 'dev' to '5.6' will happen > ~ after a week (Most probably Monday 17th Aug). > > > So please avoid creating new changes in 'dev' during next week, just finalize > ongoing changes there & start using '5.6' instead. 'dev' will be "open" for > new changes (new features etc) targeting to Qt 5.7 release after the final > downmerge. > > > br, > > Jani > > > Lähettäjä: Heikkinen Jani > Lähetetty: 3. elokuuta 2015 13:55 > Vastaanottaja: development@qt-project.org > Kopio: releas...@qt-project.org > Aihe: HEADS-UP: Qt 5.6 feature freeze and branching coming > > > Hi all, > > > According to Qt 5.6 schedule (http://wiki.qt.io/Qt-5.6-release) feature > freeze & branching from 'dev' to '5.6' should happen next Monday (10.8.2015). > How it seems, are we ready for FF after a week? > > > - Are all new modules in 'dev' already now? should be, see > http://lists.qt-project.org/pipermail/development/2015-June/021809.html > > - Are all mandatory new features in 'dev' now or coming in within a week? > > - Are new modules & features fulfilling FF criteria, see > http://wiki.qt.io/Qt5_feature_freeze > > (* List of new features in Qt 5.6 seems to be quite short, see > http://wiki.qt.io/New_Features_in_Qt_5.6 so it should be quite easy to do the > FF ;) Or the page needs some updates from feature/module owners...) > > > Is there something which prevents us to proceed as planned? Is new CI system > working well enough etc? Is Qt5.git update working ok in dev? > > > I notice from https://codereview.qt-project.org/#/c/121238/ : > > Simon Hausmann > Jul 24 5:41 AM > > Patch Set 31: Code-Review-2 > > Updates will be different > > > br, > > Jani > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Found wince info in Gerrit ,which makes me panic
> Am 17.08.2015 um 11:27 schrieb Blasche Alexander > : > >> 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 driven by getting the integration > for the serialbus module into the new CI and the module doesn't care for > VS2008 based wince. > > If you want to add wince for VS2008 feel free to fix the problem. There was > not meant to be a hidden WEC2013 comment in there beyond the fact that the > module doesn't support this either at this stage. > No i don’t care for CE < 08x00 So it just about confusing use of terms. Qt use Q_OS_WINCE for all CE versions , wec2013 too. To differentiate between CE versions the _WIN32_WCE macro value is used also for wec2013, which happens to be 0x800, while for WEC7 is is 0x700 , so internally wec2013 is WEC8. Regards, Gunnar Roth ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Nominating Sérgio Martins for Approver status
Rights have been set. Congratulations. -- Alex From: development-bounces+alexander.blasche=theqtcompany@qt-project.org on behalf of Milian Wolff Sent: Tuesday, July 21, 2015 16:38 To: development@qt-project.org Subject: Re: [Development] Nominating Sérgio Martins for Approver status On Tuesday 21 July 2015 14:43:49 Marc Mutz wrote: > On Tuesday 21 July 2015 13:27:51 Giuseppe D'Angelo wrote: > > Hi, > > > > I'd like to nominate Sérgio Martins for the Approver status in the Qt > > project. > > Oh, he's not an approver, yet? And here I was wondering why I only ever got > +1 from him :) > > +1 > > > (Disclaimer: he's a colleague of mine at KDAB.) > > Same disclaimer applies to me. +1 to both statements above. -- Milian Wolff | milian.wo...@kdab.com | Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel: +49-30-521325470 KDAB - The Qt Experts ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 4.8: disabling the CI and closing for anything except security fixes
From: development-bounces+mitch.curtis=theqtcompany@qt-project.org on behalf of Thiago Macieira Sent: Friday, 14 August 2015 22:19 To: development@qt-project.org Subject: Re: [Development] Qt 4.8: disabling the CI and closing for anything except security fixes On Friday 14 August 2015 09:41:16 Lisandro Damián Nicanor Pérez Meyer wrote: > On Thursday 13 August 2015 17:40:24 Thiago Macieira wrote: > > I recently tried to fix a very simple bug in Qt 4.8 but I can't get the > > change to integrate because the CI seems to have fallen into disrepair. > > > > Instead of using valuable QA time in fixing the CI for 4.8, I'd like to > > propose instead that we simply disable the CI for that version and close > > Qt > > 4.8 for any submission except security fixes. Gerrit would be configured > > for pure merging instead of staging, but that would only be enabled to > > Gerrit admins and they'd only do it after confirmation from the security > > team (security@qt- project.org). > > > > Any objections? > > FWIW I think this is they way to go. Seeing that we have support across the board, I'll ask the Gerrit admins to do the change. I'll also drop my fix because it's not a security fix. We can also close all Qt 4.x bug reports that do not apply to Qt 5 and aren't security issues. [snip] I created a filter for those bugs: https://bugreports.qt.io/issues/?filter=16968 I'll try to do a bulk close of those bugs and reference this thread. (Sorry about the formatting, on Windows...) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Nominating Pier Luigi Fiorini (plfiorini) as an Approver
Rights have been set. Congratulations. -- Alex From: development-bounces+alexander.blasche=theqtcompany@qt-project.org on behalf of Robin Burchell Sent: Tuesday, July 14, 2015 16:37 To: development@qt-project.org Subject: [Development] Nominating Pier Luigi Fiorini (plfiorini) as an Approver Hi, I would like to nominate plfiorini for Approver status. He's been quite helpful in working on Wayland (client & compositor) side things in conjunction with the Hawaii desktop (http://hawaiios.org/), and offering review on related patches. He also has knowledge of QPA thanks to this work, and best of all, is easy to get in touch with (and very friendly on) IRC :). His dashboard: https://codereview.qt-project.org/#/q/owner:%22Pier+Luigi+Fiorini+%253Cpierluigi.fiorini%2540gmail.com%253E%22,n,z And his reviews: https://codereview.qt-project.org/#/q/reviewer:%22Pier+Luigi+Fiorini+%253Cpierluigi.fiorini%2540gmail.com%253E%22,n,z Would anyone like to second? Robin ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Found wince info in Gerrit ,which makes me panic
>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 driven by getting the integration for the serialbus module into the new CI and the module doesn't care for VS2008 based wince. If you want to add wince for VS2008 feel free to fix the problem. There was not meant to be a hidden WEC2013 comment in there beyond the fact that the module doesn't support this either at this stage. -- Alex ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
