[mapguide-internals] Motion: post MGOS 2.0.2

[Paul Spencer]

I am anxious to get 1.1 in everyones hands and I think it is pretty  
darn stable since it has been reasonably well tested by the power  
users already.  It does require a minor change in the templates  
(replacing OpenLayers.String.translate with OpenLayers.i18n) and it is  
not purely a bug fix release.

The biggest change was the upgrade of OpenLayers from 2.5 to 2.6 and  
corresponding changes in the Fusion code to use OpenLayers functions  
for most things we were using Prototype for before (Function.bind and  
Class.create primarily).

One thing I am a bit worried about is that we'll end up skipping 1.1  
in favour of a 1.2/2.0 version that includes a new version of Jx and  
miscellaneous performance enhancements when MGOS goes to 2.1.

Given that 1.1 has already been moderately well tested in the field, I  
feel the risk is fairly low to updating and am moderately comfortable  
that folks won't have any problems.

But updating does break the release rules at least somewhat and could  
put some people at risk if they have made copies of the fusion  
templates and customized them (and who wouldn't want to do that!).

And +1 for the other stuff.

Cheers

Paul

On 9-Sep-08, at 4:22 PM, Tom Fukushima wrote:

> Jason and Andy,
>
> For an MGOS patch release, I don't think that upgrading one of the  
> libraries by more than a patch release is a good idea.  That said...
>
> Hi Paul (or anyone else who might have some input),
>
> Could you give us an idea of the risk of moving to 1.1?  The reason  
> I ask is, a MGOS patch release does not go through the same test  
> cycles as a major release, so I don't want us to put anything in  
> that is risky.  And MGOS 2.1.0 should be coming up soon anyway; so  
> that is a good time to upgrade.
>
> Thanks
> Tom
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org 
> ] On Behalf Of Jason Birch
> Sent: Tuesday, September 09, 2008 12:37 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] Motion: post MGOS 2.0.2
>
> Tom,
>
> will you be able to include Fusion 1.1 in this release?  It is in RC
> now, and should be available soon.  This fixes a LOT of problems since
> 1.0.7.  There would be some changes required to the MapGuide templates
> to account for changes in the OpenLayers localization code.  AndrewD  
> has
> done these I believe, and we may be able to get patches?
>
> Regardless, I'm +1 just for the MapGuide core fixes.
>
> Jason
>
> -----Original Message-----
> From: Tom Fukushima
> Subject: [mapguide-internals] Motion: post MGOS 2.0.2
>
> It looks like we can get some time from our build team to produce a  
> MGOS
> 2.0.2 in the next week or so.  It will have the FF3 fix in it so I  
> think
> that it will be well received.
>
> I motion that when it becomes available, we post it and announce it.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://www.dmsolutions.ca/