API backward compatibility
Hello,
|
Accepted answer
Ralph Schoon (63.5k●3●36●46)
| answered Jun 02 '17, 12:11 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Jun 02 '17, 12:17 p.m. In general we understand backwards compatibility the compatibility of a newer (higher) version to an older (lower) version, I think.
Andre Gusmao selected this answer as the correct answer
Comments
Andre Gusmao
commented Jun 02 '17, 2:59 p.m.
Thanks Ralph. I also find another post in your blog (https://rsjazz.wordpress.com/2016/11/07/the-rtc-sdk-is-about-to-change-in-6-0-3/) which helps understand the changes in the RTC SDK for 6.0.3.
|
One other answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 03 '17, 6:22 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER My understanding is that the design goal is for the OSLC APIs to be backward compatible (i.e. calls continue to work in later releases), and for the Java APIs documented in the "Plain Java Client Libraries API" on the RTC all-downloads page to be backward compatible. Also, the RTC scm command line with the -json flag specified is intended to be backward compatible.
But note that this is the design goal ... the reality may vary, so real experience from someone like Ralph is a more accurate statement on the current state of affairs.
All other API's are "buyer beware" ... they are not gratuitously changed, but if new functionality requires a change to the API, that change will be made. This includes non-OSLC REST/HTTP APIs, Java APIs not document in the "Plain Java Client Libraries API", and the RTC scm command line without the -json flag.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.