Hi all,

I'm just wondering - given a few large changes coming up, including:
- qt5 support, possibly breaking plugins
- potential composer redesign, breaking api
- geometry rework, where an api break would result in a better
foundation moving forward

... is it worth exploring the idea of making the next release QGIS 3.0
and breaking API? I know the original plan was for 3.0 to coincide
with python 3 support, but that doesn't appear to be anywhere on the
horizon yet.

Nyall
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to