[mapguide-internals] MGOS 2.0.1 status

[Mike Adair]

I was sort of planning to fix the misalignment bug as part of some 
refactoring work I'm doing to allow more than one map in a MapGroup (and 
allow other types of layers to be used).  That work should definitely be 
targeted to a 1.1 release but it sounds like I should do a patch for the 
mis-alignment issue before that.  I know what the problem is and don't 
think it would involve too much time.

Mike

Paul Spencer wrote:
> I think some of the new changes in Fusion recently are destined for a 
> 1.1 release rather than a 1.0.5 release because they are new features 
> rather than bug fixes.  I will talk to Mike early next week about the 
> state of the 1.0 branch vs trunk and try to bring over any important 
> bug fixes.  As Zac mentioned, the misalignment of the tiles seems like 
> an important fix to get in, I'm not sure of the status of that.
>
> For a potential 1.1, I think we have a few more things to go in 
> including some Jx work to factor out Prototype/Scriptaculous in favour 
> of mootools.
>
> Cheers
>
> Paul
>
> On 1-May-08, at 11:01 PM, Jason Birch wrote:
>
>> To follow up to myself....
>>
>> As long as we take the Fusion that is in trunk, I think we're good 
>> for all the fixes up to 1.0.4, which is the most current release.  
>> There were some revisions between the revision used for MapGuide 
>> trunk and the 1.0.4 release, but I think that was all SVN migration 
>> stuff.
>>
>> There are certainly some other outstanding bugs in Fusion, but 1.0.5 
>> appears to be a ways out.  Fortunately, fusion is relatively easy to 
>> upgrade (at least between point releases).
>>
>> Jason
>>
>> ________________________________
>>
>> From: mapguide-internals-bounces at lists.osgeo.org on behalf of Jason 
>> Birch
>> Sent: Thu 2008-05-01 4:25 PM
>> To: MapGuide Internals Mail List
>> Subject: RE: [mapguide-internals] MGOS 2.0.1 status
>>
>>
>>
>> That sounds great.
>>
>> Is there an updated Fusion for this build compared to 2.0?  I believe
>> that some significant bugs have been fixed since the 2.0 release, in
>> selection and maybe in some of the canvas tools (select radius, distance
>> measure, etc).
>>
>> Will we have an internal-only RC for this release, or are the changes
>> small enough that you're comfortable with an untested point release?
>>
>> Jason
>>
>> -----Original Message-----
>> From: Tom Fukushima
>> Subject: [mapguide-internals] MGOS 2.0.1 status
>>
>> Here's a status update on MGOS 2.0.1.  I was waiting to get merge
>> modules for the missing providers, but it doesn't look like that is
>> going to happen for the already released FDO binaries (we will have them
>> in future builds though).  So now we're trying to figure out which
>> version of FDO to install and once we have that I should be able to post
>> a MGOS 2.0.1.  This should all be resolved within a few days I hope.
>> _______________________________________________
>> 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/
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>