map_suite_release_cycle_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
map_suite_release_cycle_guide [2015/08/31 08:22] admin [Map_Suite_Release_Cycle_Guide] |
map_suite_release_cycle_guide [2015/08/31 08:22] (current) admin [API Compatibility] |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| ===== API Compatibility ===== | ===== API Compatibility ===== | ||
| We see API compatibility as a key concept across all of our products. We strive to ensure that each new version of the API is compatible with previous versions. Having said that, no framework is perfect and occasionally a bad API is released that we want to correct in a future version. Our approach is to mark that API as obsolete and provide guidance relating to a new API. To date we have not actually removed any obsolete APIs; however, we reserve the right to remove them after one year of being marked obsolete. This equates into one full annual release cycle. For example, An API marked obsolete in version 6.0 during May of 2012 may be removed in version 7.0 during May of 2013. As I mentioned earlier we have never done this to date, but at some point we may need to due to a buildup of obsolete APIs that may mislead developers into choosing the wrong API during initial development. | We see API compatibility as a key concept across all of our products. We strive to ensure that each new version of the API is compatible with previous versions. Having said that, no framework is perfect and occasionally a bad API is released that we want to correct in a future version. Our approach is to mark that API as obsolete and provide guidance relating to a new API. To date we have not actually removed any obsolete APIs; however, we reserve the right to remove them after one year of being marked obsolete. This equates into one full annual release cycle. For example, An API marked obsolete in version 6.0 during May of 2012 may be removed in version 7.0 during May of 2013. As I mentioned earlier we have never done this to date, but at some point we may need to due to a buildup of obsolete APIs that may mislead developers into choosing the wrong API during initial development. | ||
| - | |||
| - | [[Category:Map Suite Services Edition]] [[Category:Map Suite Desktop Edition]] [[Category:Map Suite WPF Desktop Edition]] [[Category:Map Suite Web Edition]] [[Category:Map Suite Silverlight Edition]] [[Category:Map Suite WMS Server Edition]] [[Category:Map Suite Geocoder]] [[Category:Map Suite Routing]] [[Category:Web GIS]] [[Category:Desktop GIS]] [[Category:GIS]] [[Category:.NET]] | ||
map_suite_release_cycle_guide.txt ยท Last modified: 2015/08/31 08:22 by admin