[mapguide-internals] Maestro and compatibility with previous
trevor_wekel at otxsystems.com
Thu Jul 23 15:21:17 EDT 2009
I was just looking at MapGuide subversion vault and it seems as though Maestro only has a single stream under http://svn.osgeo.org/mapguide/trunk/Tools/Maestro. Is the intent to always have Maestro trunk support all releases of MapGuide? This would currently include 1.2, 2.0, and 2.1 and likely 2.2 next year.
This will make coding and validation for new releases more complicated due to the "all releases supported" constraint. Next year's Maestro will have to be coded to ensure that 1.2, 2.0, 2.1, and 2.2 work. In addition, Maestro will have to be testing against all of these versions of MapGuide on both Windows and Linux. That's eight different combinations to validate.
It might be simpler from a coding and testing perspective if Maestro used a branch strategy similar to the one used for MapGuide. In other words, Maestro could have a separate branch for 1.2, 2.0, 2.1 and 2.2. Previous releases (1.2, 2.0) would only receive critical bug fixes and the most current release would get all the new features. Since there are different versions of Maestro available, 100% backward compatibility is no longer a requirement. Users could just install the version(s) of Maestro they required. In addition, development and testing should be easier because Maestro would only be targeting a specific release of MapGuide.
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
Sent: Thursday, July 23, 2009 6:23 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Maestro and compatibility with previous mapguide versions.
it would be good to have some sort of register of users by version n api...
On Thu, Jul 23, 2009 at 9:41 PM, Jackie Ng<jumpinjackie at gmail.com> wrote:
> 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
> - Jackie
> Gabriele Monfardini wrote:
>>> Generally I would like Maestro to be compatible with all versions of
>>> 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
>> Please continue supporting version 1.2 if it's possible (and not too much
>> 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
>>> 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
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
> 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.
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
Zac Spitzer -
+61 405 847 168
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals