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

Subversion Default Working Copy Upgrade policy

From: J.M. Becker <jm_at_mashon.com>
Date: Tue, 22 Sep 2009 10:39:52 -0700


This is J.M. Becker, i work at Mashon.com and I'm also a long time
subversion user. I work at a Linux systems/server administrator and
have done so for about 4 1/2 + years.

Before I started to work here, there was some systems neglect. The main
machines are in the process of being upgraded to newer and more stable
distros. During the movement of a cronjob like server, one of the svn
updating script ran as expected, it would. Then problem is however we
share a working directory on one development server and the svn version
there is 1.5, the version on the new machine 1.6.

as you can guess i learned about working copy automatic upgrading the
hard way. I really suggest (heck beg..) that you reconsider asking a
yes/no question right being initiating an automatic working copy
upgrade. as I ended up rendering our development machine's working copy
  unusable until i ran the python change version script. (which is not
the fastest script, especially if you have a large repository checked out.)

I just ask you please please consider added a yes/no question with a
warning about working copy upgrade and rendering older client versions

thank you so much for lichening to our issue,

J.M. Becker


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-22 19:45:26 CEST

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.