[postgis-devel] PSC Vote: Make GEOS 3.5 minimum for PostGIS 2.3

[Paragon Corporation]

Bas,

Okay I retract my request and we'll keep 3.4 as the minimum for 2.3, at least for now.  Things may change as we get closer to release.

Thank you for your input,
Regina

-----Original Message-----
From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Sebastiaan Couwenberg
Sent: Tuesday, December 15, 2015 12:39 PM
To: postgis-devel at lists.osgeo.org
Subject: Re: [postgis-devel] PSC Vote: Make GEOS 3.5 minimum for PostGIS 2.3

On 15-12-15 17:29, Paragon Corporation wrote:
> Didn't see a reply to this.  I'm willing to rescind my request if you feel it will impeded packaging.  Many reason for doing it is just to get rid of some extra legacy baggage and to ensure that all who have PostGIS 2.3 get a consistent set of functions available.

Yes, I intend to keep updating the postgis backport for stable with whichever version is in testing as long as possible. I however do not intend to backport geos and be forced to manage transitions in stable for all its reverse dependencies.

> The functions people wouldn't get if they don't compile with GEOS 3.5 
> is
> 
> ST_SubDivide
> ST_ClipByBox
> ST_Voronoi
> 
> And there may be more when we get to final release in 6-12 months.

Reduced features for earlier GEOS versions is no problem, the backport is mostly meant for the other improvements not dependent newer GEOS versions that don't warrant stable updates or security uploads.

> -----Original Message-----
> From: Paragon Corporation [mailto:lr at pcorp.us]
> Sent: Friday, December 04, 2015 10:05 AM
> To: 'PostGIS Development Discussion' <postgis-devel at lists.osgeo.org>
> Subject: RE: [postgis-devel] PSC Vote: Make GEOS 3.5 minimum for 
> PostGIS 2.3
> 
> Any other package maintainers out there who want to voice an opinion.  I apologize for not making it clear I also wanted to hear opinions, particularly from package maintainers.
> 
> Bas,
> 
> PostGIS 2.3 is probably a year away, 6 months at earliest if we are lucky.  Would you be making PostGIS 2.3 available in backports when it comes out and if so why would you not do the same for GEOS 3.5?
> For older versions of PostGIS, the minimum of what they were at time of release still remains the same for each micro-release.
> 
> Thanks,
> Regina
> 
> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On 
> Behalf Of Sandro Santilli
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] PSC Vote: Make GEOS 3.5 minimum for 
> PostGIS 2.3
> 
> On 04-12-15 01:41, Greg Troxel wrote:
>> I am  not on the PSC, but in pkgsrc geos is already at 3.5.0, so this 
>> seems ok in my corner.
> 
> I'm not on the PSC either, and Debian has GEOS 3.5.0 in unstable too, but I do not support this motion.
> 
> Requiring a GEOS version that is only available in the most recent (in
> development) distributions makes it unsuitable for backports and older releases, and distributions that haven't updated to GEOS 3.5.0 yet.
> 
> You should support what you can with GEOS 3.4 which has the widest adoption among distributions, and enable the new GEOS 3.5 features where it's available.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1 _______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/postgis-devel