Hi Michaël,

At the moment 2.14 is LTR (you probably know ;) ) and I would dissuade
from declaring another one. Here is the reason:

At least I would strongly suggest we deal with 2.18 as the latest
release in the 2.x series. But we don't know for sure, suddenly a 2.20
might pop up for whatever reason (fingers crossed there's none!)

We will continue to backport fixes to the current latest 2.x branch
(2.16 now, 2.18 soon), so at any point in time when we spot 3.0 arrival
we can declare the latest release (again, hopefully 2.18 :) ) at that
time to be LTR.

2.14 is still young. LTR was introduced for stability and infrequent
updates.

Still, this has also been discussed at a recent meeting with some people
from the Swiss User Group. Just so you know you are not alone.
I actually welcome it when (organisation) users discuss these kind of
things because LTR was introduced for them by the project. Turning this
thing around and having organisations as a solid base for the LTR (and
offer targetted funding for this) gives the LTR much more sustainability
and credibility.
I would greatly appreciate a group of (non-developer) organisation
representatives strengthening the LTR idea!

Best
Matthias

On 09/21/2016 01:33 PM, kimaidou wrote:
> Hi,
> 
> A big other question: will this release be a LTR ? I am sorry to reopen
> Pandora box, but this is a question often asked by users during courses.
> They would prefer to have the last 2.* as LTR, before the big changes,
> in order to keep their plugins and projects "safe" before 3.0.
> Or perhaps it is too soon, as we do not know yet if there will be a 2.20 ?
> 
> Regards
> Michaël
> 
> 2016-09-21 11:09 GMT+02:00 Neumann, Andreas <a.neum...@carto.net
> <mailto:a.neum...@carto.net>>:
> 
>     Hi Nathan,
> 
>     Yes - in Bonn it was decided to do a 2.18 release.
> 
>     There are a number of new features in master 2.
> 
>     The plan is also to have 2.18.x releases which will add DXF/DWG CAD
>     import support and Geopackage improvements (through OGR). Jürgen and
>     Evan will work on these. Both of these features couldn't make it
>     into 2.17.
> 
>     Andreas
> 
>     On 2016-09-21 00:33, Nathan Woodrow wrote:
> 
>>     Hi all,
>>      
>>     Are we doing a 2.18 release.  Seems we are in freeze but I wasn't
>>     sure we were doing the release to start with.
>>      
>>     - Nathan
>>
>>     _______________________________________________
>>     Qgis-developer mailing list
>>     Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists.osgeo.org>
>>     List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>     <http://lists.osgeo.org/mailman/listinfo/qgis-developer>
>>     Unsubscribe:
>>     http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>     <http://lists.osgeo.org/mailman/listinfo/qgis-developer>
> 
>      
> 
>      
> 
>     _______________________________________________
>     Qgis-developer mailing list
>     Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists.osgeo.org>
>     List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>     <http://lists.osgeo.org/mailman/listinfo/qgis-developer>
>     Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>     <http://lists.osgeo.org/mailman/listinfo/qgis-developer>
> 
> 
> 
> 
> _______________________________________________
> 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
> 
_______________________________________________
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

Reply via email to