[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Build system with CVS
From: |
Jakob Hummes |
Subject: |
Re: Build system with CVS |
Date: |
Mon, 26 Mar 2001 11:59:35 +0200 |
"Greg A. Woods" wrote:
>
> [ On Saturday, March 24, 2001 at 12:05:04 (+0100), Jakob Hummes wrote: ]
> > Subject: Build system with CVS
> >
> > We have a tag "test_tag" that identifies the latest stable version of
> > all files. Now, I want to test the new versions, but seperately. For
> > this, all developers have tagged all files of their new versions with
> > the "<developername>_tag". Obviously, the "<developername>_tag" is on
> > the same or later revisions than the "test_tag".
>
> If you're doing what I think you're doing you should probably have had
> each developer working on a private branch that you could then merge
> one-by-one to the stable branch for testing and integration.
Well, you're right. This would be a solution.
Unfortunately branching and especially merging is heavy-weight (i.e.
complicated) in CVS. Since, in general, no two branches exist for the
same file in our repository, I wanted to avoid branching if possible.
Is there a reason, why CVS does not support the possibilty to specify a
set of tags or revision numbers in the checkout or update functions,
which will checkout the latest of these revisions (if more than one
tag/revision numbres matches)?
- Jakob