<p dir="ltr">What ever we do we just can't break plugins unless it's planned out and all in one go to reduce the number of updates that need to be done </p>
<br><div class="gmail_quote"><div dir="ltr">On Sun, 25 Oct 2015 8:11 am Jürgen E. <<a href="mailto:jef@norbit.de">jef@norbit.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nyall,<br>
<br>
On Sun, 25. Oct 2015 at 06:13:22 +1100, Nyall Dawson wrote:<br>
> But keeping the possibility of merging the branch before 2.14 means the api<br>
> is locked... That's not ideal, it'll create a lot of (unneeded) extra work.<br>
> I'd say allow breaks in the branch, merge after 2.14.<br>
<br>
Well, if we explore if there is a smooth migration path to PyQt5 first, there<br>
might be a way to have 2.14 also support Qt5 and PyQt5 - so we might be able to<br>
have a 2.14 working on OSX with Qt5. That's why we're in a hurry, right? But<br>
frankly OSX is not really a priority for me.<br>
<br>
For Debian (not so sure about Ubuntu) and Windows the Qt switch is not that<br>
pressing (IIRC last time we discussed that meant after 2.14 goes out of<br>
maintaince - so no need to have both Qts, both pythons and both PyQts in<br>
OSGeo4W).<br>
<br>
Anyway, we can probably also use our findings in the new branch to update<br>
master just in that direction before 2.14.<br>
<br>
<br>
Jürgen<br>
<br>
--<br>
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br>
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50<br>
Software Engineer D-26506 Norden <a href="http://www.norbit.de" rel="noreferrer" target="_blank">http://www.norbit.de</a><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote></div>