That's rather unfortunate, but most probably needed. The issue raised, 20262, affects WMS(T), XYZ, WFS, etc. layers.
On top of - and very much due to - the gravity of the bug itself, 3.4 is flagged as LTR, and it'd be most appropriate to insure that people jumping onto this new LTR aren't left with a bad first impression. Math On Wed, Oct 31, 2018 at 8:55 AM Nyall Dawson <[email protected]> wrote: > Bah... feels like every major release someone ends up sending an email > like this... but in this case, https://issues.qgis.org/issues/20262 > has totally destroyed QGIS network based providers with Qt 5.11 and > above. > > This is not anyone's fault -- it's an upstream change in the Qt > library which changed some behavior we relied on. Not there fault, not > our fault. But end result is that it makes QGIS basically unusable for > any non gdal/ogr layers on Qt >= 5.11. And unfortunately our major > platforms only saw an upgrade to Qt 5.11 late in the bug fixing > period, which made this one slow to be identified. > > https://github.com/qgis/QGIS/pull/8383 should fix it. > > Soo.... could we break the normal cycle and get a point release out > quickly? (Ideally with a couple of days prenotice so that anyone else > working on urgent bug fixes could get them in too) > > Nyall > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
