[postgis-devel] Upcoming releases: 1.5.1

[Paragon Corporation]

Paul,

Hmm all these difficult decisions.

+1 for an rc1

+0 to go straight.

I think we should have at least one rc given the number of changes, but I
don't feel that strongly about it if others feel strongly against it :)

Thanks,
Regina

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paul
Ramsey
Sent: Monday, March 08, 2010 6:30 PM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] Upcoming releases: 1.5.1

Done, do I have your +1? :)

On Mon, Mar 8, 2010 at 1:53 PM, Paragon Corporation <lr at pcorp.us> wrote:
>
>
>> I have enough time to drop a tarball, but not enough to do any ticket 
>> closing. 1.5.1: better than nothing? Here's the list of tickets 
>> closed against the 1.5.1 milestone
>
>>
> http://trac.osgeo.org/postgis/query?status=closed&milestone=PostGIS+1.
> 5.1&or
> der=priority
>
>> Probably there are some other issues that have been closed, but 
>> against the 2.0 milestone.
>
>
> Paul,
>
> Any chance we can get this bug fixed before we release.
>
> http://trac.osgeo.org/postgis/ticket/410
>
>  It affects both 1.4 and 1.5 branches (and also 1.3/1.2 etc but I can 
> live without 1.3 being patched I suppose).
>
> I had mistakenly thought it was only a 1.4 issue.  Below is a test to 
> prove
>
> CREATE TABLE foo ()WITH (OIDS = TRUE); SELECT AddGeometryColumn( 
> 'foo', 'the_geom', -1, 'LINESTRING', 2); SELECT AddGeometryColumn( 
> 'foo', 'the_geom2', -1, 'LINESTRING', 2); INSERT INTO foo(the_geom, 
> the_geom2) VALUES (ST_GeomFromText('LINESTRING(0 0, 1 3)'), 
> ST_GeomFromText('LINESTRING(0 0, 1 3)')); UPDATE foo SET 
> the_geom=ST_SetPoint(the_geom, 0, 'POINT(100000 200000)'); SELECT 
> st_astext(the_geom), st_astext(the_geom2) FROM foo; SELECT 
> st_astext(ST_Envelope(the_geom)), st_astext(ST_Envelope(the_geom2)) 
> FROM foo;
>
> SELECT ST_Box2D(the_geom),  ST_Box2D(ST_ASText(the_geom)) FROM foo;
>
>
> ---- This returns an erroneous cached box on my 1.5 install which screws
up
> spatial query results.
> BOX(0 0,1 3);BOX(1 3,100000 200000)
>
> I consider it somewhat critical, since I still have hack code to
compensate
> for this defect that would be nice to get rid of and since we changed the
> name of DropBbox etc. my hack code has to be different for each version of
> PostGIS now.
>
> Also I do believe Devrim asked about both 1.5.1 and 1.4.2
>
> Thanks,
> Regina
>
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel