[mapguide-internals] Release of MGOS 1.2.0

[amorsell]

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 2008.

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.

Andy

----------------------------------------

From: "Tom Fukushima" <tom.fukushima at autodesk.com>
Sent: Thursday, June 21, 2007 12:33 PM
To: "MapGuide Internals Mail List" <mapguide-internals at lists.osgeo.org>
Subject: [mapguide-internals] Release of MGOS 1.2.0 

Hi PSC members, 

I know our release process says that the final release can occur 2-3
weeks after the final release candidate, but I motion to make RC2 our
final release this Monday barring any severe problems. 

One thing that needs to be done is to update the online API docs to the
1.2 version; I think that for this I need to update subversion, then
submit a ticket to SAC to run an update on the site right?

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals