[mapguide-internals] RE: API Operation Version Confusion

[Jason Birch]

That makes sense to me too.  Using the web api version rather than a function-specific revision adds a lot of value.

I guess my question though is, how do we move to consolidate on this system without causing backwards compatibility issues?  Is it too late to standardise on this system and gain value from it?

Jason

-----Original Message-----
From: Dave Wilson
Sent: Monday, August 17, 2009 1:01 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RE: API Operation Version Confusion

I'm not sure what the standard for this in open source, but logically the version reflects the version the API was introduced in or updated in. If it hasn't been updated the version wouldn't change. This would act like a label so that you can find all the 1.0.0 APIs, the 1.2.1 APIs (or revisions) and so on. That would seem like useful information to me. If an API doesn't have a 1.0.0 version you know it was introduced later.

-----Original Message-----
From: Bruce Dechant
Sent: Monday, August 17, 2009 1:51 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] API Operation Version Confusion

I would like to discuss the confusion on the API version information.

Currently, all of the APIs have an associated operation "VERSION". This "VERSION" hasn't been clearly defined and after looking at the latest code base we are using it inconsistently throughout the project.

As you can see we have not been following a well defined operation "VERSION" scheme and this is something we need to correct as it is confusing.