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

Re: TortoiseSVN 1.7.14 ?

From: Thomas Harold <thomas-lists_at_nybeta.com>
Date: Fri, 02 Aug 2013 15:56:57 -0400

On 8/2/2013 3:06 PM, Mike Beasley wrote:
> Hi,
>
> We're still using the Subversion 1.7 here.
>
> A new Subversion version 1.7.11 was
> recently released (on July 24th).
>
> Will a new version of TortoiseSVN that's built
> for use with Subversion 1.7.11 be created?
>
> If not, is it reasonable to continue to use
> TortoiseSVN 1.7.13 to access Subversion 1.7.11 ?
>

Unless there is some specific bug/feature fixed in a particular version,
AFAIK the version of the server vs the version of the client doesn't
matter much. Our SVN server went from 1.6 to 1.7 to 1.8.1 and we have
yet to upgrade clients to 1.8.1. Most of our client desktops/laptops
are running a mix of TSVN 1.6 and TSVN 1.7, with one early adopter
running TSVN 1.8.1.

Having both the client and server on the same revision (both running
1.8) gives you more capabilities then a 1.7 client talking to a 1.8 server.

http://subversion.apache.org/docs/release-notes/1.7.html
http://subversion.apache.org/docs/release-notes/1.8.html

(As a rule, I generally wait 2-3 weeks after a new major release like
1.7.0 or 1.8.0. Which is why we're just now rolling out 1.8.1.)

If you are instead talking about using two different clients (the
command line client and the TortoiseSVN client) to access the same local
working copy folder, then it matters a lot more. But since TSVN now
ships with a command line client, it's easy to keep both in sync.

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-02 21:57:09 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.