[postgis-devel] PostgreSQL 9.5.0 has just been stamped

[Paragon Corporation]

Greg,

Couple of clarifications

1) PostGIS 2.2.0 will work with PostgreSQL 9.5.0 fine as far as my testing
has determined and our bots do test against the 9.5 releases.
2) The rush is mostly since packagers I know like to get all things
together, we just want to put our best foot forward and PostGIS 2.2.1 has a
ton of bug fixes not present in 2.2.0.  
We'd hate packagers packaging 2.2.0 instead of 2.2.1 when they roll out 9.5
when we've put all this effort in 2.2.1

3) I called for a planned release about 2 weeks ago and have been running
like I'm live all this time and doing a lot of tests.  So this isn't
something that we decided just yesterday.
Granted the time frame between freeze and release could be longer (like we
could actually freeze things), but not sure we are ready for that.  
We aren't as big as PostgreSQL YET anyway in terms of devs and just
mindshare to allow that luxury.

4) 2 outstanding changes left which I'm going to push to the next milestone
if they are not fixed by tomorrow sometime
https://trac.osgeo.org/postgis/query?status=assigned&status=new&status=reope
ned&milestone=PostGIS+2.2.1&col=id&col=summary&col=status

Greg - if you could verify these 2 changes work for you that would be much
appreciated:

https://trac.osgeo.org/postgis/ticket/3390

https://trac.osgeo.org/postgis/ticket/3415


Thanks,
Regina



-----Original Message-----
From: Greg Troxel [mailto:gdt at ir.bbn.com] 
Sent: Monday, January 04, 2016 8:56 PM
To: Paragon Corporation <lr at pcorp.us>
Cc: 'PostGIS Development Discussion' <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] PostgreSQL 9.5.0 has just been stamped


"Paragon Corporation" <lr at pcorp.us> writes:

> Slight correction.  PostgreSQL 9.5.0 has been stamped, not yet released
:).
> Packagers embargo is on.
>
> So we still have probably 1-2 days so to catch the train.

I am really not following this.  Are you saying that postgis-current does
not work with 9.5.0?  Or that 2.2.0 doesn't?  And are you implying that
somehow postgis is expected to work immediately when there is a new
postgresql version?   I don't see the panic; 9.5.0 is by definition
bleeding edge, and certainly is going to take a at least a little bit to
show up in packaging systems.

If postgis is supposed to work with new postgresql versions, then it seems
clear that there has to be a regular process of testing with the postgresql
branches leading up to release well before the release happens.

Doing anything in a several-days trimeframe seems like a recipe for
mistakes.

Sort of separately, I'm not sure what the 2.2.1 plan is, but given that
people have other things to do, it seems there should be a more-or-less
freeze with a week for people to pre-package and check things.  It will
probably take me an hour to test.  It seems the time to test is now, as it
feels like no more changes are planned.