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

Re: stabilization & number of changes

From: Mike Mason <mgm_at_thoughtworks.net>
Date: 2004-01-08 15:35:08 CET

Greg Stein wrote:

>On Wed, Jan 07, 2004 at 11:00:03AM -0500, mark benedetto king wrote:
>>You're right; there are hoardes of people waiting for 1.0 to adopt svn.
>>I'm one of them. The cost of an API change is probably proportional
>>to the number of users; let's try to injure only the early adopters,
>>rather than the masses.
>One of my underlying reasons for avoiding API changes right now is that
>you can view the set of available software as a sort of "ecosphere" of
>tools around SVN. If we change the API now, then it ripples throughout
>that entire ecosphere and tightly couples versions of each against each
>other. If we tweak the API, then suddently RapidSVN no longer works. The
>user will have to upgrade that. Oh, and their buddy's Windows box will
>need a new TortoiseSVN to deal with the new SVN. etc.

But that's true of anything that's compiled against a library, isn't it?
If I upgrade Subversion on my server, I probably have to upgrade my
clients. I'd then at least have to upgrade the library that Tortoise is
(dynamically?) linking against. I do agree that changing the API will
cause ripple effects, but I think a lot of people developing tools are
waiting for the magic 1.0 stabilisation line before themselves doing a
final push to work with Subversion.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 8 15:35:27 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.