Release Candidate 3

[Steve Lime]

The GEOS WKT support suffers from the 2D/3D issue. I didn't see that as a big deal for the first go round. It should handle the multipart features though. It's up to you if you'd like to tackle any of that before RC3. I'm not going to do anything more to the GEOS support unless someone finds a true bug.

I see your already tracking 1613 down so we should definitely wait on that one.

Steve

>>> Frank Warmerdam <warmerdam at pobox.com> 01/19/06 7:27 AM >>>
On 1/18/06, Steve Lime <steve.lime at dnr.state.mn.us> wrote:
> Hi all: In case you weren't reading the WKT thread, Frank suggested doing a RC3 based on the latest flurry of changes. The WKT stuff hasn't really been tested broadly so it's worth it. Thoughts?
>
> I'm ready to cut a release once the source has been tagged.

Steve,

There are two recent bugs:
  http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1613
  http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1618

I am wondering if we should push to fix them for 4.8 (in
which case they ought to be fixed before RC3) or just leave
them for 4.8.1.

The WKT issues relate to fairly esoteric geometry types (in
my mind), though they need to be fixed at some point.   The
"imagemap" bug seems like it could affect alot of other things
too if we are not ever using vsnprintf().  For instance handling
of long error messages.   To me this is worth delaying the
release (and RC3) for.

Best regards,

--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent