[PROJ] Future maintainance releases

[Kristian Evers]

> On 30 Oct 2019, at 14:45, Greg Troxel <gdt at lexort.com> wrote:
> 
> Bas Couwenberg <sebastic at xs4all.nl> writes:
> 
>> [info about proj6 migration status]
> 
> From my perspective on packaging many things, proj's trajectory of
> deprecations is already feeling very rapid compared to how many things
> depend on it.   Realize that people are still in the process of getting
> off qt4.
> 
> pkgsrc is in a similar position to Debian, although less well baked,
> with proj6 in wip (sort of like Debian unstable, but not really), and
> having to define ACCEPT_USE_OF_DEPRECATED_PROJ_API_H to keep some things
> building.
> 
> I don't want to have multiple proj versions in pkgsrc,a nd I don't want
> to prclude libosmium, libspatialite, mapnik.
> 
> I feel that the "rip the bandaid off" notion is counterproductive, as it
> really means "break things for users so that packagers have to decide
> between old proj and dropping dependencies”.

I don’t think that is a fair way to lay it out. From the beginning we've had
a “double-feature” in the release schedule for the 7.0.0 release with an
accompanying 6.x-release. This is still the plan and if it turns out to be
necessary we can put out more releases of the 6.x branch later on. Users
of proj_api.h should be taken care of for at least a year or two more with
the 6.3.1 release. But at some point support for 6.x has to stop. I don’t
want to see us move into Python2 territory!

/Kristian

> 
> The real question is whether removing it would be a real gain, or just a
> club to get people to update.  Certainly it's going to happen, but I
> think it would be good to let the dust settle on proj6 first.  It feels
> like we as a larger osgeo community are making progress on that and in 6
> months or so I'd expect the situation is much better.
> _______________________________________________
> PROJ mailing list
> PROJ at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/proj