Adam Winter wrote:

>
>First, how can two products share a module? We have an 
application, and as 
>usual that consists of modules. Soon we will be creating a 
second 
>distinctly different application that will exist in parallel 
with the 
>first, and share most, but not all of its modules. We want 
changes made to 
>one module to be propagated to all applications that use it.

This is going to be an issue with your tree-structure more than 
anything.  The important thing is not to create copies of 
modules within CVS.  That way you don't really have to propagate 
anything, its all in one place.  The various workspaces that use 
those modules will have to issue a "cvs update" command to get 
the latest version but that's about it.

In order to limit checkouts to the modules you need for each 
application you can use the modules file.  This is explained in 
the Cederqvist manual.

>
>Second, we would like to be able to check in our source and at 
the same 
>time indicate levels of stability. This way I could work on a 
module and 
>repeatedly check it in, but to my own area isolated from 
others, and once 
>it is stable, check it into the main development trunk. Based 
on my 
>reading, I'm thinking that the way to do this is by each person 
having his 
>or her own branch and merging back into the main trunk when 
appropriate. Is 
>there a more elegant solution?
>

I would say that's the best way to isolate your work.  Each 
person then has history and it isn't affecting anyone until they 
merge.  

For informational purposes, you can use the "cvs admin -s" 
command to specify the status of a version.  The default state 
is "Exp" for "Experimental".  Whenever we do a release we do a 
"cvs admin -sReleased".  You could use other names as well, like 
"Stable", "Unstable", "Broken", etc.  

I am not sure if you can use these for your checkouts, though.   
I don't think so.  It would be nice to be able to do "cvs co 
-SStable" to get the latest stable release.

-- 
Stephen Rasku                   E-mail: [EMAIL PROTECTED]
Senior Software Engineer        Web:    http://www.tgivan.com/
TGI Technologies                        http://www.pop-star.net/

Reply via email to