[postgis-devel] PostGIS 2.5 what should be minimum requirements?

Fri Sep 29 11:13:57 PDT 2017

PostGIS PSC, Stakeholders, All -

  I believe there is a certain weight to the conencted graph of 
components, that has to do with other implementors, technical strength,
interoperability, luck, and other factors.. 

  Specifically, a certain very large project is re-writing their 
geometry handling with their own libraries, and rejecting GEOS at the 
same time. 
Therefore, GEOS is less of a stand-alone component in the future, and 
due to packaging realities, is problematic for a requirements chain. 
Regina observed that "the way people are going to get GEOS in the 
future is with GDAL" and I concur. 

  So reduce or eliminate GEOS version requirements, and focus on the 
GDAL version. 
This is ironic, since initially GDAL for PostGIS raster caused huge 
drag on the packaging efforts, due to circular depends. 
But in this proposed future, the PostgreSQL version + GDAL version 
would be the markers, and the rest of the chain follows . 

  hth -Brian

On Fri, 29 Sep 2017 16:28:31 +0000, Darafei "Komяpa" Praliaskouski  wrote:

       Please don't hesitate to raise minimum versions to latest 
released at the time of release. 
If someone needs an older version, they are free to comment out the 
checks and build at their own risk. 
Otherwise we're going to have distros with older versions of libraries, 
because "it's not required to upgrade so let's not". 

If somebody updates postgis outside of their distro's release cycle, 
they're doing it at their risk already, so no reason not to drag newer 
libraries in. Usually they don't break too much ABI to postpone. 

пт, 29 сент. 2017 г. в 17:55, Daniel Baston :

       This is tangential to this specific proposal, but I am wondering 
whether we should establish some general rules for how long to support 
old versions of dependencies. 
For example, we could decide to support  in new versions of PostGIS 
until  after  is released.  As an example, we could decide to support 
GEOS 3.4 in new versions of PostGIS until 2 years after GEOS 3.5 is 
released. 

Or alternatively, we could say that we support the latest released 
version of , plus any versions released within the past .  So we could 
decide to support GEOS 3.6, plus any versions of GEOS released in the 
past three years (3.4 dates back to 2013, so this would limit it to 3.5 
and 3.6). 

I'm just throwing these out for the sake of examples, but I think some 
guidelines along these lines could help make these decisions simpler 
and more predictable for users/packagers. 

Dan

On Fri, Sep 29, 2017 at 10:40 AM, Regina Obe  wrote:

       While we are still in infancy of PostGIS 2.5 (and probably at 
least a year
away from release), I'd like to get requirements out of the way and propose
the following:

1) Drop support for PostgreSQL 9.4 and 9.5  (so PostgreSQL 9.6 - PostgreSQL
11 will be supported)
9.4 has the main annoyance of not supporting true KNN and I'm tired of
explaining this to folks and having people with pg_upgrading from these
lowers being screwed when upgrading because they can no longer do

ALTER EXTENSION ...  cause they are already at 2.5.0

9.5 doesn't support Parallelism and I suspect we may need to do some
restructuring for some aggs in 2.5, I'd just assume not have to make special
concessions for folks trying to pg_upgrade from a PostgreSQL 9.5 2.5
extension to 9.6+

2) Make GEOS 3.5+ the minimum (for 2.4  GEOS 3.4 was the minimum)  - we've
got too much stuff that requires 3.5 already that is turned off for lower
and newer GEOS has some robustness improvements. 

3) Make Proj 4.9+ the minimum currently our minimum is proj 4.7 I think.  As
discussed it's on the table to redo some of the geography stuff like
ST_Segmentize using proj 4.9+ features. 

Anyone have issues with the above?

PSC folks, if you are okay with all the above please give a +1

If you are okay with some and not others, I can break apart so we can at
least decide on some pieces. 

Thanks,
Regina

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-devel

-------------------------

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-devel

--
Brian M Hamlin
OSGeo California
blog.light42.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20170929/b9da5d2c/attachment.html>