[fusion-dev] Defects and branch for MapGuide 2.2
Trevor Wekel
trevor_wekel at otxsystems.com
Thu Jun 24 18:38:11 EDT 2010
Yep. That sounds perfect. I think the RFC89 changes have already been submitted to trunk.
Thanks Mike!
Trevor
-----Original Message-----
From: Mike Adair [mailto:madair at dmsolutions.ca]
Sent: June 24, 2010 11:18 AM
To: Trevor Wekel
Cc: fusion-dev at lists.osgeo.org
Subject: Re: [fusion-dev] Defects and branch for MapGuide 2.2
So because of this and the of RFC89, it means that at some point Fusion
will not be backward compatible with MGOS before v2.2. I discussed this
with Paul and we propose the following release schedule for Fusion:
- v2.0 finish up and finalize this release; other than regressions, I
would like have any outstanding projection issues resolved for this release
- we skip v2.1 just so that the version numbers are in synch for MGOS2.2
- just for this release
- v2.2 a new branch from trunk to be released along with MGOS2.2 with
changes for RFC89 and the GetSiteVersion changes (and any other issues
identified as important) - this is not backward compatible with MGOS < 2.2
- v2.3 will be the merge of the Jx3 branch back to trunk
Comments?
Mike
On 6/22/2010 1:40 PM, Trevor Wekel wrote:
> Ok. Thanks Mike.
>
> I also have another patch to replace the call with MgServerAdmin.GetInformationProperties with a call to MgServerAdmin.GetSiteVersion. I will open an enhancement for it as well. GetInformationProperties was recently mutexed to fix another defect. As a side effect, the multiuser performance for LoadMap.php dropped. GetSiteVersion does not require the mutex and is significantly faster.
>
> Regards,
> Trevor
>
>
> -----Original Message-----
> From: Mike Adair [mailto:madair at dmsolutions.ca]
> Sent: June 22, 2010 10:32 AM
> To: Trevor Wekel
> Cc: fusion-dev at lists.osgeo.org
> Subject: Re: [fusion-dev] Defects and branch for MapGuide 2.2
>
> Trevor,
>
> Both of those involve correcting the projection support so I'd like to
> get those into the 2.0 release, and I hope to have some time free up
> this week to look at them and finalizing the 2.0 release. The Fusion
> 2.0 branch will likely be your best bet for including in MGOS2.2 since
> once that is released we will be working on the 2.1 which will include
> updates to the OL and Jx libraries and may introduce other issues.
>
> Mike
>
>
> Trevor Wekel wrote:
>
>> Hello list,
>>
>>
>>
>> Has there been any further discussion on how to resolve
>>
>>
>>
>> http://trac.osgeo.org/fusion/ticket/394
>>
>> http://trac.osgeo.org/fusion/ticket/395
>>
>>
>>
>> They are basically the same issue with Arbitrary XY coordinate
>> systems. If an appropriate fix is too far out, can I request a Fusion
>> branch for MapGuide Open Source 2.2?
>>
>>
>>
>> Regards,
>>
>> Trevor
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> fusion-dev mailing list
>> fusion-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/fusion-dev
>>
>>
>
--
Michael Adair
Senior Software Architect
DM Solutions Group Inc.
Office: (613) 565-5056 x26
madair at dmsolutions.ca
http://www.dmsolutions.ca
http://research.dmsolutions.ca
More information about the fusion-dev
mailing list