Re: Question on multiple repositories

[Kaz Kylheku]

On Thu, 4 Apr 2002, Max wrote:

> Date: Thu, 04 Apr 2002 01:23:18 GMT
> From: Max <address@hidden>
> To: address@hidden
> Newsgroups: gnu.cvs.help
> Subject: [info-cvs] Question on multiple repositories
> 
> 
>  I'm brand new at the CVS game and have no senior resource available at
> work, so I'm hoping that I can get some help here.
> 
>  The specs I was handed at the office call for an open development
> repository and a secure QA/production repository. 

This is nonsense; everyone can work from the same repository. 

> Once developers finish
> their stuff, a baseline is made and the code is replicated to the QA
> repository.  This is the step where I'm having a problem.

CVS can assign a symbolic revision to the baseline. This is done using
cvs rtag.  A branch can be made from the symbolic revision when
critical bugs need to be fixed in a build that is identified as a
release candidate. So no separate repository is needed to stabilize
code.

If you really want a stable second level repository, simply use
CVS's import feature to import snapshots on the vendor branch. That is,
treat the devoper team as a third-party source code ``vendor''.

> which at this time is empty.  I set my CVSROOT to point the development,
> check out based on a tag, then try get the code into the QA repository.
> First I set my CVSROOT to point to the QA repository, then use "commit" to
> move the code.  Alternatively, since there are no modules in the QA
> repository, I try to use "add".  Both fail because I still appear to be
> pointing to the development repository.
> 
>  I'm hesitant to use "import" because (as I understand it) this command will
> club the previous versions under the same name (down the road).

No, import does not club anything, it adds new versions.

>  So the question I have is how do I move source from one repository to the
> other?  Is there a way to save the baseline and the version numbers in the
> process.

Not without copying the RCS files themselves, which simply gives you an
exact replica of the repository, not a different repository that
contains only the stable baselines you want.

-- 
Meta-CVS: solid version control tool with directory structure versioning. 
http://users.footprints.net/~kaz/mcvs.html