[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: svn1.7.x compatibility issues

From: Alexander Stohr <alexander.stohr_at_gmx.de>
Date: Fri, 28 Oct 2011 01:12:55 -0700 (PDT)

terminology - to my experience any source management repository (and i know at least half a dozend of them) was able to develop its very own set of nomenclatura and wording family for whats happening in a specific system (even if it has its equivalent in other systems)... sandbox, tip, toe, branch, trunk... i think you got it right.

compatibility - see http://tortoisesvn.net/tsvn_1.7_releasenotes.html#compatibility
"Compatibility concerns

Older clients and servers interoperate transparently with 1.7 servers and clients. However, some of the new 1.7 features may not be available unless both client and server are the latest version. There are also cases where a new feature will work but will run less efficiently if the client is new and the server old."

this was no concern for me so i tried it. (would you judge your risk any different when the lines read all will cope fine with each other?)

a BIG hint in this section for these other sections "Centralized Metadata Storage" and esepcially "Upgrading the Working Copy" with the terminating lines:
*** "Once you've upgraded your working copies, older SVN clients won't be able to access those working copies. So make sure that you update all your SVN clients (in case you use not just TortoiseSVN)." ***
...would be a good idea.

lets hope someone can fix this for the release notes.
regards, Alex.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2865733

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-10-28 12:21:39 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.