Hi Nyall >- geometry rework, where an api break would result in a better >foundation moving forward
For the geometry rework, it is not a problem to keep compatibility with 2. It is even an advantage, as there is more time to adapt the numerous pieces of code that work with QgsGeometry.
I think it is to early to go for version 3, 2 has been released a bit more than a year ago.
Regards, Marco On 08.11.2014 07:11, Nyall Dawson wrote:
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 [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
-- Dr. Marco Hugentobler Sourcepole - Linux & Open Source Solutions Weberstrasse 5, CH-8004 Zürich, Switzerland [email protected] http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
