[postgis-devel] Planned 2.5.0beta1 in next couple of days

[Regina Obe]

I've merged this PR and put in the #ifdefs logic to prevent PG < 11.

 

One thing on my plate to do is verifying that going from PG 10 (or lower) running 2.5.0  to PG 11 2.5.0 installs the new operator class and functions.

I'll do that before final release.

 

Aside from that I think all that is left for this is user documentation on how to install spgist indexes.  That doesn't need to happen before 2.5.0beta1 release.

 

Only other note – which I made a note of in pull request is removing the static decorator on some of our existing functions which was part of the PR. Not sure if that is kosher with all as it does expose more than I think we want exposed in the library.

 

If that's all, I'm looking to push a beta1 release tomorrow.

 

Thanks,

Regina

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Darafei "Kom?pa" Praliaskouski
Sent: Saturday, June 30, 2018 4:26 AM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] Planned 2.5.0beta1 in next couple of days

 

пт, 29 июн. 2018 г. в 20:04, Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> >:

I presume everyone has all their core changes in place?


I need help merging https://github.com/postgis/postgis/pull/258.


It currently lacks #ifdefs for disabling the code for PG <11. It passes make check locally for me on PG11, we weren't yet able to get PG11 regress pass on travis even for vanilla PostGIS which is primary reason for me this PR hangs.

 

With SP-GiST merged, the rest of things on my mind can be pushed to 3.0.

 

If it lacks docs or polishing of some kind, I'll have a chance to properly sit down and dig in after July 10.

 

If you consider the merge of SP-GiST impossible right now, I ask to lift the freeze for SP-GiST specifically until the end of July.

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