On Wed, Oct 14, 2015 at 11:19:44AM +0200, Richard Duivenvoorde wrote: > ps my personal idea: > > Work hard on 2.14 AND docs for it, to be the last but most stable > 2.x > version ever by being very carefull about what put in 2.13 (maybe a > (big)feature freeze) > Then after 2.14 concentrate on moving to Python3/Qt5, so general > users > can stick to 2.14 for a loooong time, and dev's have some extra time > to > get the 3.0/Qt5/Python3 work done?
+1 to make 2.14 a longer-term release (2 years ?), I don't see a drawback to that (the weekly-silence rule makes it so that if there's nothing to fix, there's nothing to release, reducing the maintainance cost over time). Now the question is: when would a QT5 compatible version be needed ? And, would it be ok for it to not be an LTR before Feb 2017 ? --strk; _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
