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

RE: Re: Subversion vs Clearcase

From: Irvine, Chuck R [EQ] <Chuck.R.Irvine_at_Embarq.com>
Date: 2007-04-27 19:20:48 CEST

[snip]
>
> In my opinion there are two main features that Subversion
> lacks in comparison with ClearCase. Without these I think
> there are valid cases where a team would not want to switch
> to Subversion.

These are things are a big deal to us as well, but...

>
> 1) Lack of merge tracking

1. After you get used to it, keeping track of revision boundries when
merging isn't *that* bad.
2. It seems that svnmerge.py works fairly well, though we've just
experimented with it so far so. There may be issues we don't know about.
3. Finally, merge tracking supposedly is coming in 1.5.

>
> ClearCase has very mature merge tracking capabilities (via
> merge arrows). Subversion has none. You must track what has
> previously been merged either by hand or do all merges in the
> svnmerge.py script.
>
> 2) True rename support

Hmmmm..... Yes this is problem for the reason. :-|

>
> See
> http://svnbook.red-bean.com/nightly/en/svn.branchmerge.copycha
> nges.html#svn.branchmerge.copychanges.bestprac.moves.
> This problem means that merging from one branch to another
> when moves or renames have occurred can be an extremely
> manual process and in some common cases you could accidently
> delete changes from one branch. Of course those changes are
> still in the repository, but the merge deletes them without warning.

Actually, the same underlying problem, can cause code loss from the
latest revision even in the context of a single development stream, i.e.
the trunk, when one user renames something and another makes edits and
does an update.

>
> So if a team can live with ClearCase's limitations regarding
> how close the client is to the server and they have intense
> branching and merging requirements, my opinion is that
> ClearCase is a better fit.

Another factor is the cost of ClearCase in terms of initial cost, annual
maintenance, hardware, networking enhancements, internal support costs.
All of this can add up to a substantial sum. If you start adding CC's
replication functionality, costs are even more substantial.

>
> Justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 27 19:21:24 2007

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

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