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

RE: Re: Disable tortoiseSVN from Automatic upgrading to 1.5 client

From: Todd Carmichael <toddc_at_concur.com>
Date: Wed, 9 Jul 2008 12:32:20 -0700

I understand. Thanks
Sounds like a shared library/.dll approach is needed for clients.
IntelliJ is 'hard' linked with subversion 1.4 client bits.
If you are a developer using tools to build code and don't know this SVN
migration/upgrade policy and Tortoise displays the friendly message "You
are running 1.4.x and the latest is 1.5, go upgrade" you can easily and
unknowingly hose yourself.
Very few members of our team would know these details. Of course, they
are learning them now the hard way.

My feedback...

-----Original Message-----
From: Jean-Marc van Leerdam [mailto:j.m.van.leerdam_at_gmail.com]
Sent: Monday, July 07, 2008 10:25 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: Disable tortoiseSVN from Automatic upgrading to 1.5 client

Hi Todd,

On 08/07/2008, Todd Carmichael <toddc_at_concur.com> wrote:
> Huh? Where is the creative thinking here? It could be a feature that
> defaults to 1.5 and has to be configured for 1.4.
> Why does it have to be so black and white?
>

Subversion policy is to deliver compatibility between servers and
clients from the same major release number and between clients of the
same minor release number(at least the minor release number of the
subversion libraries these clients use). This already poses a burden
on the development teams of the Subversion core and the Subversion
clients out there.

It is also not possible to allow a 1.5 client to use a 1.4 working
copy format or the other way around, since the bookkeeping
requirements for each version vary. If the Subversion developers were
to support this, the time to market for new features would increase
dramatically (backwards/upwards compatibility has its price), or it
could even prevent adding features unless customers did a client &
server upgrade at the same time.

When using Subversion you need to have two upgrade strategies (one for
the server side and one for the client side) that are related to each
other but not necessarily require upgrades on both ends at the same
time.

And it is possible to have working copies dedicated to specific
Subversion clients (you can use a 1.4 client to connect to a 1.5
server). When combined on a single working environment it is up to the
user to make sure he does not touch a 1.4 working copy with 1.5
clients.

-- 
Regards,
Jean-Marc
----------------
    ___
   // \\  @@     "De Chelonian Mobile"
  / \_/ \/._)    TortoiseSVN
 <\_/_\_/ /      The coolest Interface to (Sub)Version Control
  /_/   \_\      Check out http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-09 21:32:28 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.