Client and server compatibility in 2.x

Moved from inside another post - my mistake:

On Tue, 05 Jan 2010 13:08:03 +0000, kesterto wrote:

Hi all

I am working with a team with RTC 2.0.0.0 installed, and they are
looking to move to the latest 2.0.0.2. Their clients are generally
Windows XP, servers are RHL.

Can they leave some users on the 2.0.0.0 client, or do they need to
upgrade all clients at the same time as the server?

As a followup - assuming they can leave some clients at 2.0.0.0 - how
can we work out what functionality they will lose from 2.0.0.2?

thanks

anthony

Yes, 2.0.0.2 clients will be compatible with a 2.0.0.0 server and vice-
versa.

To see the changes in the new versions, you can go to the download page
for that release and click on the "New & Noteworthy" link. Here is the
link for the changes from 2.0.0.0 to 2.0.0.1:
https://jazz.net/downloads/rational-team-concert/releases/2.0.0.1?p=news

And here's the link for changes from 2.0.0.1 to 2.0.0.2:
https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2?p=news

--
Jared Burns
Jazz Process Team

Thanks Jared - the compatibility is going to help a lot.

How about the other part of the question - is any of that new functionality invisible to 2.0.0.0 clients (and I am specifically thinking of the new approvals functionality)?

thanks

anthony

Yes, any new functionality which is listed in the new and noteworthy which is in the clients (Visual Studio, Eclipse, or command lines) will require an update of the clients.

The only forcing client adoption is if teams start versioning symbolic links, clients for the teams that load those files will need to be updated.

However, if you don't need the new features in the UIs of the clients (eg, configuring new process rules, etc..) then client updates are not required at all.

Cheers,
Jean-Michel