[postgis-devel] PSC Vote postgis, postgis-raster: ready ?

[Regina Obe]

> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On
> Behalf Of Sandro Santilli
> Sent: Wednesday, September 05, 2018 11:20 AM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] postgis, postgis-raster: ready ?
> 
> On Mon, Sep 03, 2018 at 12:06:35PM -0400, Regina Obe wrote:
> > -1, maybe I'll change my mind later but we've got other serious issues in
> postgis 3.0 like lots of bots failing.
> 
> I ticketed ONE reason for bots failing:
> https://trac.osgeo.org/postgis/ticket/4170#ticket
> 
> Dronie is catching an upgrade issue: our upgrade mechanism refuses to soft-
> upgrade from 2.x to 3.x (did we have a policy about naming versions to only
> increment Major for dump/restore
> requirements?)
> 
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
[Regina Obe] 
Let me check on the bots and see what's up with Winnie and Debbie.  I'll try to do that today.

I'm still not fond of the idea of breaking out raster/ postgis into separate extensions especially now that everyone has gotten used to them being together.
Upgrades are going to be messy as to insure proper upgrades, people will have to learn to use our new function if they are using raster - https://postgis.net/docs/manual-2.5/PostGIS_Extensions_Upgrade.html
Then again I guess it will be easier for people who don't want raster.

I would have liked it encoded in the version, but I guess dependency wise, might be better to if we are going to do this,
have it as separate so that if other extensions rely on raster, they can explicitly say depends on postgis_raster.

Seems Dan and Darafei want this though. Hmm tough.

That said - I'll change my vote to a +0.5

Bborie and Paul, can you vote on this.

Thanks,
Regina