Hi Nyall, You just beat me on the same email a few minutes away :-)
> - Get PSC to vote on and accept > https://github.com/qgis/QGIS-Enhancement-Proposals/issues/29 . Needs > to be done ASAP so that we're all agreed that 2.14 is the last 2.0 > series release. +1 > - Decide on the timing for 3.0. Specifically, will the normal > scheduled release after 2.14 be skipped to allow for a longer > development cycle for 3.0. Regarding this, my opinion is that we NEED > the longer cycle to allow room for the (non Qt5/python 3.0) related > changes which we can ONLY make for an API breaking release. There's > already a long list at https://github.com/qgis/qgis3.0_api/issues, and > I suspect this is only scratching the surface. Without sufficient time > for devs to address these API related issues we'll be stuck with the > limitations of the current API for another 2-3 years. +1 > Anyway, can we please lock in point 1 above so that we can move the > discussion on to timing? +1 for approving point 1 ASAP. Vincent _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
