[mapguide-internals] Maestro and compatibility with previous mapguide versions.

[Jackie Ng]

The flipside to that is that the need to support 1.2 may hinder certain
enhancements from being implemented. Which is why I raised the original
question.

- Jackie


Gabriele Monfardini wrote:
> 
>> Generally I would like Maestro to be compatible with all versions of
>> MapGuide.
> 
> Great.
> 
>> But versions older than 1.2 are not supported, and once 2.1 comes out,
>> I think 1.2 support could be deprecated.
>> And by deprecated I mean, just not accept tickets fixing issues with that
>> version.
> Please continue supporting version 1.2 if it's possible (and not too much
> work).
> 
> Some people is still using 1.2 due to some problem with 2.x (eg.
> horrible compilation problem under GNU/Linux or problems with new
> Postgis provider).
> And Maestro is a great tool to work with.
> 
> 
>> So far, MapGuide has not broken any backwards compatibility, so
>> when implementing a new feature everything else should work fine anyway.
>>
>> I only have access to a few versions of MapGuide, so I generally only
>> test
>> with the most recent release (2.1 atm).
> 
> Well, obviously this is fine.
> Until now 2.x API is largely the same as 1.2 so no problems at all.
> Thank you for your work
> 
> Gabriele
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> 

-- 
View this message in context: http://n2.nabble.com/Maestro-and-compatibility-with-previous-mapguide-versions.-tp3307965p3309041.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.