Option (1): ability to use old and new clients together without new
(Provided the error message they get when they do use incompatible
features is helpful.)
This way we can roll out new clients (such as TortoiseSVN), but still
attempt to successfully
use old Eclipse versions that may not have updated Subclipse plugins.
We regularly have "old projects" resurrected for small changes that may
not want to pay
the penalty of upgrading the whole build environment.
However, since I lived through it once, I'm sure I'd survive option (2)
"David Glasser" <firstname.lastname@example.org>
Sent by: email@example.com
10/04/2007 03:14 PM
"Karl Fogel" <firstname.lastname@example.org>, email@example.com, "Erik
Huelsmann" <firstname.lastname@example.org>, "Jack Repenning" <email@example.com>,
"Mark Phippard" <firstname.lastname@example.org>, "Ben Collins-Sussman"
Re: We should bump WC format version number for 1.5.
On 10/4/07, email@example.com <firstname.lastname@example.org>
> Having gone through the extreme pain of upgrading 2000 users in a
> corporate environment from 1.3 to 1.4 and seeing many have multiple
> incompatible clients installed, I'll take anything that makes it
> less painful. We even have projects that are forced to use certain
> versions due to environment lock downs or contract agreements. If
> one person is working on 2 projects requiring different versions
> things get very messy.
Kevin, I think we all agree there.
The question is, what is less painful:
* Users who never use non-default depths being able to use both
versions simultaneously and invisibly, but use of depth may
surprisingly trigger an upgrade months after you first upgraded svn.
* Nobody is able to mix 1.4 and 1.5 clients in the same working
directory, but this becomes obvious as soon as you try to use both,
no matter whether or not --depth has been used.
David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
Received on Thu Oct 4 22:56:24 2007