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

Re: Impact on clients of upgrading server 1.2->1.4

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-07-04 16:00:22 CEST

On 7/3/07, Douglas Pearson <biz@sunnyhome.org> wrote:
> We have a repository running SVN 1.2.3 and it seems like it's time to move
> up to 1.4 (the current repo is giving some errors which may have been
> fixed).

Normally, nothing special needs to happen on the clients side when you
upgrade the server. The protocol is transparently defined and older
clients just don't request any of the newer functionality. The reverse
is also true, btw: when a newer client detects that a server doesn't
support a certain kind of newer functionality, it will resort to the
older equivalent, if that exists.

> My question is will we need all users to upgrade to a 1.4 client if we do
> this?

No, except if you expect to access the users working copies with the
version you installed on the server. (1.4 has a newer working copy
format, which affects client side transitions)

> Also is there anything special we need to do on the server end? The FAQ
> seems to suggest a dump/restore is the safest way to upgrade.

I'd recommend a good backup, but when you don't move to another
server, there's no need for a dump/restore. If you do, however, you
can take advantage of some speed optimizations built into 1.4 which
aren't available in the older repositories.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 4 16:00:28 2007

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

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