4.6.0 final today

[Daniel Morissette]

Paul Ramsey wrote:
> Fair enough, I can back down, I only really had the opportunity to 
> heavily test in the last two days, two months lead time notwithstanding. 
> Having run across some of the other quirks recently as a result of that 
> (Intersect vs Intersects) I am somewhat sensitive: broken standards 
> support is almost worse than none at all (as it raises expectations 
> before they are dashed).
> 
> <PAUSE>
> 
> So, I downloaded CadCorp MapBrowser, and it worked with mapserver 4.4 
> and 4.6. Only one problem, and that was when it was given a LineString 
> with only one coordinate (not legal GML). Which is a data or a server 
> problem, depending on where one wants to point fingers.
> 

MapServer should probably produce an error (or exception) in mapgml.c 
instead of returning a LineString with a single vertex. I have filed a 
bug for this:
http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1380


> So I feel better that our 4.6 problem is very likely self-inflicted and 
> not something I should worry about in a larger context. Fire away, sorry 
> for the tempest.
> 

Cool. For other readers of the list, in addition to Tom's test reports 
in this thread, there was also an off-list report from Bart who said 
that he also tested succesfully with Cadcorp Mapbrowser, so I think we 
can be confident that things are not plain broken and that what you ran 
into may be an isolated issue (in MapServer or in uDig) that can be 
dealt with later.

Thanks to all who responded quickly. Moving on with the release now.

Daniel
-- 
------------------------------------------------------------
  Daniel Morissette               dmorissette at dmsolutions.ca
  DM Solutions Group              http://www.dmsolutions.ca/
------------------------------------------------------------