[postgis-devel] 2.0.4 ?

[Paragon Corporation]

You did for 2.1 branch as well. Remember trunk is 2.2.

Also please backport to 2.1 for this:
http://trac.osgeo.org/postgis/ticket/2307  if its necessary to do so. 

-----Original Message-----
From: postgis-devel-bounces at lists.osgeo.org
[mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Thursday, July 04, 2013 7:00 PM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] 2.0.4 ?

I committed handling for two-digit version numbers through all our operative
branches (1.5+) and trunk, so we should be OK as GEOS continue to rev up.
P

On Tue, Jul 2, 2013 at 12:46 PM, Paul Ramsey <pramsey at cleverelephant.ca>
wrote:
> I'll look at the GEOS support in configuration, since we're going to have
to cross that bridge probably.
> P
>
> --
> Paul Ramsey
> http://cleverelephant.ca/
> http://postgis.net/
>
>
> On Wednesday, 26 June, 2013 at 9:35 AM, Sandro Santilli wrote:
>
>> I got the testcase, but I shall notice that PostGIS build scripts are 
>> currently using a single digit for each version component of GEOS, so 
>> releasing 3.3.9 will force us to change that as soon as we need to 
>> support 3.3.10 :)
>>
>> Add to it that there are currently 13 open tickets with milestone 
>> GEOS 3.3.9:
>>
>> http://trac.osgeo.org/geos/query?status=assigned&status=new&status=re
>> opened&order=priority&col=id&col=summary&col=status&col=type&col=prio
>> rity&col=milestone&col=component&milestone=3.3.9
>>
>> I think it takes more time before getting it out of the door.
>>
>> --strk;
>>
>> On Wed, Jun 26, 2013 at 02:14:20PM +0200, Sandro Santilli wrote:
>> > On Wed, Jun 26, 2013 at 03:39:12AM -0400, Paragon Corporation wrote:
>> > > Strk it would be nice if you released GEOS 3.3.9 first don't you 
>> > > think :)
>> >
>> >
>> >
>> > For packagers ? Possibly.
>> > I was +1 on PostGIS 2.0.4 because it wasn't ME having to do it :)
>> >
>> > A GEOS-3.3.9 could be done, but I'm waiting for a testcase about 
>> > HotPixel code first.
>> >
>> > --strk;
>> >
>> > >
>> > > -----Original Message-----
>> > > From: postgis-devel-bounces at lists.osgeo.org 
>> > > (mailto:postgis-devel-bounces at lists.osgeo.org)
>> > > [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of 
>> > > Sandro Santilli
>> > > Sent: Wednesday, June 26, 2013 3:26 AM
>> > > To: PostGIS Development Discussion
>> > > Subject: Re: [postgis-devel] 2.0.4 ?
>> > >
>> > > On Tue, Jun 25, 2013 at 03:35:25PM -0700, Paul Ramsey wrote:
>> > > > It's been 3 months since the last 2.0 point release and a 
>> > > > moderate number
>> > >
>> > >
>> > > of fixes have built up, anyone object to a 2.0 patch release?
>> > >
>> > > Changes, for the record:
>> > >
>> > > PostGIS 2.0.4
>> > > 2013/MM/DD
>> > >
>> > > * Bug Fixes *
>> > > - #2110, Equality operator between EMPTY and point on origin
>> > > - Allow adding points at precision distance with TopoGeo_addPoint
>> > > - #1968, Fix missing edge from toTopoGeom return
>> > > - #2201, ST_GeoHash wrong on boundaries
>> > > - #2257, GBOX variables not initialized when testing with empty 
>> > > geometries
>> > > - #2271, Prevent parallel make of raster
>> > > - #2267, Server crash from analyze table
>> > > - #2277, potential segfault removed
>> > > - Fix build with systemwide liblwgeom installed
>> > >
>> > > * Enhancements *
>> > > - #2269, Avoid uselessly detoasting full geometries on ANALYZE
>> > >
>> > > +1 for me to release 2.0.4
>> > >
>> > > --strk;
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org (mailto:postgis-devel at lists.osgeo.org)
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>
>
>
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel