Re: [QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
On Tue, 28 Jan 2020 at 19:50, Jürgen E. Fischer wrote: > BTW which is the version that has the fixes we contracted KDAB on? V 13.1 Nyall > > > Jürgen > > -- > Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 > Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 > Software Engineer D-26506 Nordenhttps://www.norbit.de > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
Hi, On Tue, 28. Jan 2020 at 09:27:30 +1000, Nyall Dawson wrote: > > "The offline installer will become available to commercial licensees only" > This is the biggest impact. I understand that osgeo4w qt libraries are based > off the offline installer packages (correct me if I'm wrong here Jürgen!). > The consequence of this is that we'd need to self-build Qt libraries for > inclusion in osgeo4w and the QGIS installers. Outcome: more work for the > Windows installer maintainers̶. I tried to avoid the building because that takes ages - and we maybe have other advantages by using the "standard" binaries. I originally thought that we could also upgrade the compiler with the update, but the compiler we were already using was the last the installer offered 32 and 64bit builds - at the time - so I kept using that. qtwebkit had to be built extra anyway - which is also huge (maybe even larger than Qt itself) and later I found that qtwebengine wasn't builtin as well, which is also a huge build. So I'm not sure that using the installer instead of building myself saved much at all. IIRC webkit used to be the most time consuming part of the build in earlier versions. Another side note: azure pipelines will phase out the image carrying the 2015 compiler we use in march - not sure if we can install 2015 on the fly, that was what didn't work in github workflows (producing an internal compiler error at some point)… BTW which is the version that has the fixes we contracted KDAB on? Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Nordenhttps://www.norbit.de signature.asc Description: PGP signature ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
Hi all Il 28/01/20 00:27, Nyall Dawson ha scritto: > Here's my analysis of the impact it will have on QGIS thanks for the analysis Nyall, quite reassuring. Juergen, any further comment? Cheers. -- Paolo Cavallini - www.faunalia.eu QGIS.ORG Chair: http://planet.qgis.org/planet/user/28/tag/qgis%20board/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
On lundi 27 janvier 2020 17:35:22 CET Paolo Cavallini wrote: > Thanks Even. As I read it, this essentially means we are more or less > forced to use the latest version, not the LTS (or to stick to an older > one). This could mean more bugs. QGIS sources aren't bound to a particular QT version. Currently the requirement is just >= 5.9 So pretty much depends on what binary distributions actually ship. I've tried to follow the discussion on the thread announcing it at https://lists.qt-project.org/pipermail/development/2020-January/thread.html#38316 but it is still unclear if QT Company will publish the source of their LTS branches or not. At the very least, bugfixes that apply to the latest -dev branch, and older branches, will be available, so people can *potentially* backport them (pending extra burden for FOSS QT, typically Linux ones, distribution maintainers to scrutanize what must be backported, which according to [1] would be very hard to do). If they don't publish the source of the LTS branches, and a bug only affects a LTS branch and not the latest -dev branch, then non-commercial customers will not benefit from it. A lot of speculations in the above thoughts, and from a outsider of the working of the QT project. If QT Company has the ultimate say to which branches are maintained or not, or if other companies might jump in to bring back public LTS support... Anyway, somewhat related to the above considerations, it looks like as far as OSGeo4W is concerned, there's a QT 5.11.3 release with security fixes (cf [2]) whereas 5.11.2 is shipped now. But as the 5.11 branch is no maintained anymore, it is well possible that 5.11.3 contains know issues, including security related ones, fixed in later versions. The 5.12 series is (should we say "was" now ?) announced as the LTS one with support until 5.12.2021 according to [3], so could be (have been?) a good candidate to track. Perhaps some upgrade policy should be defined (only makes sense if there's manpower to implement it of course) Even [1] https://lists.qt-project.org/pipermail/development/2020-January/038388.html [2] https://www.qt.io/blog/2018/12/04/qt-5-11-3-released-important-security-updates [3] https://en.wikipedia.org/wiki/Qt_version_history -- Spatialys - Geospatial professional services http://www.spatialys.com ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
On Tue, 28 Jan 2020 at 02:34, Paolo Cavallini wrote: > > Thanks Even. As I read it, this essentially means we are more or less > forced to use the latest version, not the LTS (or to stick to an older > one). This could mean more bugs. > Any deeper insight? > Cheers. It's an unexpected move, but I can honestly understand the rationale behind it. Here's my analysis of the impact it will have on QGIS (using quotes from https://lists.qt-project.org/pipermail/development/2020-January/038316.html) > "One is a change in policy regarding the LTS releases, where the LTS part of > a release is in the future going to be restricted to commercial customers. > All bug fixes will (as agreed on the Qt Contributor Summit) go into dev > first. Backporting bug fixes is something that the Qt Company will take care > of for these LTS branches. We’ve seen over the past that LTS support is > something mainly required by large companies, and should hopefully help us > get some more commercial support for developing Qt further." Doesn't greatly affect us, since this change mainly has distro level impact. Of our supported platforms, we have: - linux: Qt releases are a distro responsibility, so no direct impact to us there. Distros will either need to manually backport fixes from Qt current releases to older releases, or update more frequently to newer Qt releases. I can understand this will be painful for distro level Qt maintainers, but for our users there's likely to be minimal impact, and possibly we'll see a **better** end user experience IF distros decide to start updating Qt major releases more frequently. - mac: Zero impact. The mac builds use infrastructure that regularly updates to the current Qt versions and don't use LTR releases. - Windows: Zero impact -- osgeo4w doesn't use Qt LTR releases, and doesn't regularly update Qt versions. It's done on an ad-hoc basis and will likely continue this way On the flip side, if this move increases the revenue stream and viability of the Qt company, then it's a GOOD thing for us. > "The second change is that a Qt Account will be in the future required for > binary packages. Source code will continue to be available as currently. This > will simplify distribution and integration with the Marketplace. In addition, > we want open source users to contribute to Qt or the Qt ecosystem. Doing so > is only possible with a valid Qt Account (Jira, code review and the forums > all require a Qt Account)." Almost zero impact. A bit of annoyance for the handful of QGIS developers who build QGIS using custom (non distro) Qt versions or who use upstream Qt Creator releases, but likely all those already have Qt Accounts for use on the Qt bug tracker. > "The third change is that The Qt Company will in the future also offer a > lower priced product for small businesses. That small business product is btw > not limited to mobile like the one Digia had some years ago, but covers all > of Qt for Device Creation." Zero impact. Lastly, from https://www.qt.io/blog/qt-offering-changes-2020 : > "The offline installer will become available to commercial licensees only" This is the biggest impact. I understand that osgeo4w qt libraries are based off the offline installer packages (correct me if I'm wrong here Jürgen!). The consequence of this is that we'd need to self-build Qt libraries for inclusion in osgeo4w and the QGIS installers. Outcome: more work for the Windows installer maintainers̶. Nyall ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
Wow, strange move for Qt ! We still lack a lot of detail though... Régis Le lun. 27 janv. 2020 à 17:25, Even Rouault a écrit : > Hi, > > Just read this: > > https://www.phoronix.com/scan.php?page=news_item=Qt-Going-More-Commercial > > Even > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
Thanks Even. As I read it, this essentially means we are more or less forced to use the latest version, not the LTS (or to stick to an older one). This could mean more bugs. Any deeper insight? Cheers. Il 27/01/20 17:25, Even Rouault ha scritto: > Hi, > > Just read this: > https://www.phoronix.com/scan.php?page=news_item=Qt-Going-More-Commercial > > Even > -- Paolo Cavallini - www.faunalia.eu QGIS.ORG Chair: http://planet.qgis.org/planet/user/28/tag/qgis%20board/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] FYI: Qt LTS Releases To Be Restricted To Commercial Customers
Hi, Just read this: https://www.phoronix.com/scan.php?page=news_item=Qt-Going-More-Commercial Even -- Spatialys - Geospatial professional services http://www.spatialys.com ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
