On 2007-10-04 12:00:07 -0700, David Glasser wrote:
> The advantage to the former is simplicity: it is easier for a tool
> author (for example) to say "as soon as you use the new version you
> will need to upgrade your other tools" than something more nuanced
> like "as soon as you use the new version and use depth features, you
> will need to upgrade your other tools".
The second one can be simplified: "as soon as you use depth features,
you will need to upgrade your other tools". Then I find it easier to
say "as soon as you use depth features, you will need to upgrade your
other tools" than "as soon as you use the new version you will need
to upgrade your other tools". Users are not always admins. Therefore
they don't necessarily know what version is being used for some part
of the tools, in particular in heterogeneous networks.
I use working copies via NFS and have access to them from various
machines (e.g. Debian/stable, Debian/unstable...), which don't
have the same versions of the system tools. So, I would be very
annoyed not to be able to use my wc any longer on some machines
if I updated the wc from a machine with a recent svn version.
IMHO, when there must be a wc version bump, there should be a long
enough period where both versions are supported by the latest svn
client (this means that if the user wants to stick to the older wc
format, he may not be able to use every feature, but anyway, if he
wants such features, he won't be able to use the older svn version).
Now, concerning GUI clients for clueless users, they can have a
confirmation dialog (or expert mode) to prevent users from doing
> The advantage to the latter is that users who don't use the depth
> features can happily use 1.4 and 1.5 tools together on the same
> working copy, making the upgrade much smoother... as long as they
> don't use --depth.
This is exactly my case, and the case of most users who work in my
Vincent Lefèvre <vincent_at_vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Oct 5 15:19:26 2007