RTC Client and Server Version Strategy
I am looking to outline a strategy to keep our installation of RTC up-to-date with the most recent stable release. What I would like to know is what client version to provide to developers. Should I strive to match the RTC server version or can I let it fall behind by a few revisions without worrying. What is ideal/recommended?
Thanks, Craig |
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 20 '12, 2:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
It is guaranteed to work if you use a client version that is the same as
a server version. The current policy is that you should be able to use a client that is one release earlier (where only the first and second digits matter). So, since the next release after 3.0.* is 4.0.*, you can use a 3.0.* client with a 4.0.* server. Note that this wasn't true for the 3.0.* server ... i.e. you couldn't use a 2.0.* client against a 3.0.* server. Cheers, Geoff On 2/20/2012 12:38 PM, craffel wrote: I am looking to outline a strategy to keep our installation of RTC Comments How about the scenario where the server is 3.0.1.1 and the client is 3.0.1.2 ?
Geoffrey Clemm
commented Jan 02 '13, 3:16 p.m.
| edited Jan 02 '13, 3:22 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
With RTC, even fixpacks follow the "client version must be no greater than the server version" rule, so a 3.0.1.2 client is not guaranteed to be compatible with a 3.0.1.1 server. Work item RTC servers at version N should support (newer) clients from fixpack releases N.0.0.x (237832) requests that applying a fixpack not break compatibility. Please feel free to add a comment to this work item, indicating your interest/support. (Note: This comment replaces my earlier incorrect comment that you should be able to a fixpack to a client without breaking compatibility). |
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.