Tortoise Versioning - does it REALLY matter?

Other than the fact that each version of Tortoise svn typically adds new features or changes up some ways to do things to improve the process...I don't see any problem with using the latest. I've worked for .coms, small, and huge companies and nobody has ever worried about this.

Now if you're new and you're trying to stick with what the team has, because in case any instructions go out to help you then you might want to stick with whatever the rest of the team is using.

For me, I'm very comfortable with Tortoise. It's no big deal for me to figure out how to do the same way as an older version in a newer version if that particular functionality has changed.

However I'm wondering...or I assume basically that the underlying repository (Subversion) is always going to be consistent. That using x version of tortoise svn won't matter in terms of meta data being stored, etc.

Is this a correct assumption and if so where did you find info on that because I 开发者_如何学Chaven't seen anything that really talks about this.

the problem is not if someone else uses your working copy, but if you use a different client. In this case the newer client would upgrade the working copy format and the older one would then by unable to access it.

I upgraded Tortoise once and suddenly my Ankhsvn client refused to work - as the WC had been upgraded to 1.6 by Tortoise, but Ankh hadn't yet been recompiled to work with svn 1.6. The opposite would hold true too. You may think this is not an issue you'll ever come across (maybe so), but sometimes you will want a security fix or update and then it will matter.

I would recommend upgrading every time a new tortoise comes out - the point versions are very backwards compatible and even if there was a problem you can just downgrade it without problem. You will want the new version when subversion 1.7 is released so upgrade then too. (I read the occasional post here about people running svn 1.4 or older, you don't want to be them - upgrade, the subversion team is very good about backwards compatibility and painless upgrades, but upgrading 3 or 4 versions up isn't going to be as painless as upgrading 1 major version).

What matters in terms of collaboration is not Tortoise (the shell), but Subversion itself (the core). For example, let's assume that you have some working copies that might be used by more than one developer, possibly using more than one SVN client. If such a working copy is still in 1.5 format and you touch it with a 1.6 client (and perform some non-trivial operation), it'll automatically upgrade the working copy to 1.6 format, rendering it uselell for 1.5 clients. See Subversion 1.6 Release Notes - Working Copy and Repository Filesystem Format Changes. (Of course, you should avoid shared working copies, but that's a different story.)