When we ship a new version of iTest with bundled open source services like svn and cvs integrations, all it implies is that we have tested that in house for compatibility with iTest and Eclipse plugins.
There is no magic to "interoperability" of various pieces of software working together other than testing. So what I would recommend is to make a copy of iTest installation folder and use software update on that instance and test new version of svn on it. If everything works, you are OK to upgrade to newer version of SVN plugins.
If you look at the feature dependency tree:
Eclipse Platform ---> iTest
|
|------> SVN
Of course, this is a very simplistic view of dependencies. Dependencies are expressed in terms of minimum version of the feature/plugin they are dependent on. iTest 3.3 uses Eclipse 3.3 platform. So if you upgrade SVN feature and new SVN feature depends on Eclipse 3.4 platform, Eclipse/iTest will not allow you to upgrade. But if new SVN feature can work with Eclipse 3.3 platform, your upgrade should be successful. Even after this, you should definitely test the new version of SVN feature on a separate copy of iTest before unleashing it on rest of the testers in the group.
