Hello Nathan, > Personally I think we should still do 2.8, LTR it, and then we can do 3.0 for > the next release. > > Breaking the API again without a LTR in place makes me nervous as the 2.0 API > really wasn't that long ago.
+1000 for LTS I am with you: please, stop to change the api. If we like new functions, please add them, without change old ones. Thank you Roberto > > - Nathan > > On Sat Nov 08 2014 at 4:11:34 PM Nyall Dawson <[email protected]> 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 > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
