[postgis-devel] PostGIS 1.4 RC1 vote

[Paragon Corporation]

Mark,

Well few people know about the coumpund curve in polygon so I doubt anyone
is using that particular feature.  I didn't even know it was supposed to
work until someone mentioned it in our book review :) (I assume that was
Mark L who would know enough to mention it and have so many intimate details
:) .

I'm kind of sorry I pointed it out :(

If it's a short fix then sure, but don't want to hold up a release for it.

 I'm not saying we should make the Pg 8.4 deadling.  Just don't want to lose
the momentum when everyone is all settled in their new comfy PostgreSQL 8.4
1.3 surroundings.  They aren't going to want to upgrade.

And since we made a change to such a critical piece, we really need an RC
now.

Thanks,
Regina

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Mark
Cave-Ayland
Sent: Monday, June 29, 2009 6:15 PM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] PostGIS 1.4 RC1 vote

Paragon Corporation wrote:

> No I'm saying we never claimed to and even our documentation says we 
> don't
> 
> http://postgis.refractions.net/documentation/manual-svn/ch04.html#id30
> 63602

I think the documentation update was just something that Mark missed while
working on it. From SVN log on lwgparse.c:


r3821 | mleslie | 2009-03-10 00:29:32 +0000 (Tue, 10 Mar 2009) | 1 line

Moving parser changes from spike/mleslie/parser to allow the proper 
nesting of compound curves within curve polygons and the validation of 
compound curve continuity.  This also resolves GBT#124.


The issue I have is now PostGIS will crash rather than display a flat 
out error message like it did before, and this behaviour must be fixed 
before we push out 1.4. Given the size of the patch (and the fact we are 
really close to release), I think that the best solution would be to 
give Mark a chance to fix this; it's his code and so he will have a much 
better idea of what needs to done.

I don't see the need for us to feel pressured to push 1.4 out just to 
meet the 8.4 deadline; people have seen the beta announcement on the 
mailing list and so they know it's coming anyday - I'm sure a couple of 
days extra wait to get this one feature right won't hurt. Given that 
we've had no bug reports on 1.4 beta except #210 then I think there is 
probably a reasonable case for missing the RC and heading straight to 
final...


ATB,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel