Re: CVS vs ClearCase, was RE: cvs -n update vs cvs diff

[Greg A. Woods]

[ On Tuesday, October 22, 2002 at 14:01:12 (-0700), Johnson, Susan wrote: ]
> Subject: CVS vs ClearCase, was RE: cvs -n update vs cvs diff
>
> How should a working directory be used? What should
> be done within it, and what should be done in a 
> separate working directory?

Well, that's really entirely up to you and your project and how (if it's
a multi-person project) your team works together.

For example if you're working on a relatively large program and you have
rather diverse responsibilities to the project you might have several
working directories "active" simultaneously, one for each major change
you're working on, whether it be some new feature, or fixes on release
branch(es), etc.

Persons responsible for building releases and testing might have working
directories "open" on each release branch as well as the main
development branch(es) (which might be the trunk, depending on how you
use branches in your project).

> And how should the status of the files within one's
> working directory be determined?

With "cvs status", "cvs -n update", "cvs diff", etc. of course!  ;-)

> I'm used to ClearCase, where a person worked within a
> dynamic view and you could build, label (tag), branch,
> merge and do everything within the same workspace.
> 
> How does CVS differ from that model?

I believe the answer, at least on a conceptual level, is:  not very much.

The "view" in a given working directory in CVS can be dynamically
changed without acquiring a new workspace.

However as I suggest above you might actually want several workspaces if
you're doing rather un-related things simultaneously.

-- 
                                                                Greg A. Woods

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