[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: refactoring when using CVS

From: Greg A. Woods
Subject: RE: refactoring when using CVS
Date: Fri, 22 Feb 2002 17:09:27 -0500 (EST)

[ On Friday, February 22, 2002 at 07:12:39 (-0800), Noel Yap wrote: ]
> Subject: RE: refactoring when using CVS
> --- "Greg A. Woods" <address@hidden> wrote:
> > CVS is not and has never been very useful for
> > initial development under
> > any methodology that doesn't involve sharing of the
> > code under
> > development (and sharing in a non-XP manner!).
> I disagree.

then you are, sadly, disillusioned, and perhaps that explains why you
don't always grasp how to make effective use of CVS.

>  SCM by definition is the identification of what goes
> into a product and the control of changes into that
> product.  You seem to think that it's just the latter.

You are very wrong in your interpretation of what I think.
(as you often are, sadly)

The link between configuration and change management is much tighter
than you seem to realise.

> It's news to me 'cos you work under a different
> definition of SCM than the rest of the world.  Here's
> what I found when I did a google on "configuration
> management definition"

OK, and what part of those definitions do you believe are in any way
contrary to what I said about SCM coming into its full use after you've
made the first release?

> The original discussion, AFAIK, was comparing
> ClearCase and CVS.  I made a statement saying that CVS
> is not _ideal_ (it is usable, though) when
> refactoring.  If you look at ClearCase, it handles
> refactoring with ease even under a concurrent
> development environment.  Of course, you're also
> correct that refactoring requires fore-thought, it is
> a part of design after all.  However, with CVS, you're
> more apt to be forced to serialize development while
> refactoring while other tools handle it more
> gracefully.

It all depends on what you mean by "refactoring".

The refactoring required by XP does not necessarilly happen at the
implementation level, at least not initially (implementation naturally
follows, but the effect will be different than what happens when you
refactor an interface in the implementation).

                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]