[mapguide-internals] RE: Release of MGOS 1.2.0
amorsell at spatialgis.com
Tue Jun 26 20:26:28 EDT 2007
Yes, my experience is that it is considerably less stable with 1.2.0. This
is not emperical by any means, but based on experience with different
customer datasets. As far as I know, these issues have been introduced with
1.2 and were not a problem in 1.1:
The most significant being the former where we are seeing instability so
severe that it locks up the server and is very easy to replicate. Some of
the changes that Haris and Jason made last week helped, but Jason reported
that he was still having problems when testing with 4 simultaneous sessions.
I do agree that there are many improvements in 1.2.0 that would immediately
benefit the community, but I'm afraid that the volume of raster problems
people will run into will be significant. I would be in support of
releasing with the caveat that raster support NOT be included AT ALL and
will instead be released as a stable and tested patch in the near future.
Tom Fukushima wrote:
> Is 1.2.0 less stable with rasters than 1.1.0? If it is then I think that
> we could consider waiting for Haris, otherwise, there are many
> performance improvements in 1.2.0 that the community can benefit from so
> it still seems worthwhile to get it out.
> The reason I would like to release is that I don't see new defects
> (especially regressions) coming in. There is no relationship with this
> release and MGE---this MGOS release has been delayed for so long that it
> is of no use to current MGE development.
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of
> Sent: Saturday, June 23, 2007 12:02 PM
> To: mapguide-internals at lists.osgeo.org
> Subject: re: [mapguide-internals] Release of MGOS 1.2.0
> Checking email for the first time in the last few days and may not be
> able to again until Wednesday.
> I have to vote -0 on this. I have been heavily using the 1.2.0 betas
> and RC's in a customer environment with real-world data and there are
> simply too many unresolved issues with rasters where I am not
> comfortable releasing until those issues are firmly resolved. My
> opinion is strong enough on this topic where I would vote -1 but don't
> want to be the bad guy who vetoes the motion. I read the remainder of
> the thread on this topic and fully agree with Jason. In short, I don't
> think we should push out the release until it is ready. I don't know
> what other motivational factors there are, other than possibly Autodesk
> needing the 1.2.0 release before adopting it for use as the core of MGE
> At this point, I also realize that the primary developer resource
> working on anything GDAL is Haris and that he will not be back for at
> least a week. But, I still feel it would be prudent to stall the
> release until these issues are fully resolved and the new fixes are
> incorporated into the install packages.
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
View this message in context: http://www.nabble.com/Release-of-MGOS-1.2.0-tf3960836s16610.html#a11316327
Sent from the MapGuide Internals mailing list archive at Nabble.com.
More information about the mapguide-internals