Tim Sutton said: > Personally I was hoping for 2.18 LTR to last from June 2017 to June 2018 > and then releasing 3.2 In June 2018. > > * retire 2.14 in June 2017 > * 2.18 becomes LTR from June 2017 to ***June*** 2018 > * 3.0 feature freeze in July 2017 > * release 3.0 in Sept 2017 > * release 3.2 as next LTR in release 3.0 + 4 Months (eta June 2018).
...and Paolo said: > sorry, I think this should be > * release 3.2 as next LTR in release 3.0 + 4 Months (eta Jan 2018). What about making 3.2 a normal editon and then release 3.4 LTR? So: * 2.18 becomes LTR from June 2017 to June 2018 * release 3.0 in Sept 2017 * release 3.2 in January 2018 * release 3.4 LTR in June 2018 Other options would be: retire 2.18 LTR in January 2018 or postpone 3.2 until June 2018. Both look unacceptable for me. Who would deploy an LTR for a half an year? With dropped 2.14 support and 3.0 too young we'll be left without any stable version. And postponing the 3.2 release would only restrain the process of testing and maturation of QGIS 3. Regards, Borys _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
