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

client version vs. server version

From: Hamilton Link <helink_at_sandia.gov>
Date: 2003-12-02 23:10:37 CET

Well, I think svn is approaching the point that I am going to start
using it at work instead of cvs. I am concerned about having to play
the moving-target game with the client systems as I go from version to
version on the server, though.

If I have a svn server and a number of people running svn clients
scattered around, what determines when they have to upgrade their
client software? Do they need to upgrade every time the server is
upgraded, or do they only need to upgrade when some specific piece in
the new server version changes (and does this happen all the time,
sometimes, or only rarely)? I know the database needs to be dumped
before upgrading and reloaded afterwards if the database format changes
(and that such changes are loudly announced and probably won't be done
between the release of 1.0 and some substantially later version unless
some major upset happens, right?), but I can't think of ever having
heard about forced client upgrades.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 2 23:11:05 2003

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

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