On 12/21/06, Edward Rudd <erudd@netfor.com> wrote:
>
> On Tue, 12 Dec 2006 14:37:54 -0500, Mark Phippard wrote:
>
> [snip]
> >
> > The primary feature that most users have been looking for is Subversion
> > 1.4.x client support. This release now includes the SVN JavaHL 1.4binaries
> > for Windows as well as the latest version of SVNKit (formerly JavaSVN)
> which
> > includes support for 1.4 working copies as well as adds support for the
> > file:// protocol. So you can now access local repositories using the
> SVNKit
> > client interface, in addition to the JavaHL interface that has always
> > supported it.
> >
>
> Ahh Crap!!!. What if I don't WANT the 1.4.x client support!!! I was
> expecting that to be pushed out as a 1.2.0 version of subclipse so as to
> not cause compatibility issues. Now one of my users upgraded subclipse
> and it auto upgraded the WCs thus making his command line client no longer
> able to work with them, and causing other havoc because I never expected a
> MAJOR change like that to be pushed out in incremental release of a
> product.
Why not just update the command line? If you follow the mailing list at
all, I bet we get 10 requests for adding 1.4 for every one that doesn't want
it. What are we supposed to do? No matter what we do someone is going to
be pissed.
Your choices are to update the command line to 1.4. or downgrade the user to
1.0.3 and re-checkout their projects. Obviously I wish the SVN devs had
allowed a switch or something to control the WC format, but they did not, so
there is nothing we can do about it. We have to make a choice, no matter
what the choice is, some people are not going to like it.
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on Fri Dec 22 01:54:31 2006