[Top][All Lists]

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

RE: Problems with uncommitted working directories, from homeand w ork.

From: Jim.Hyslop
Subject: RE: Problems with uncommitted working directories, from homeand w ork.
Date: Tue, 2 Dec 2003 14:20:11 -0500

Larry Lords [mailto:address@hidden wrote:
> I have a question on Jim's statement "Private branches are 
> never considered
> candidates for releases or for builds".  I have always 
> understood that a company
> would always release from a private branch.  This assumes 
> when a release process
> begins a release branch is created and final testing begins 
> on the release
> branch's code while development for succeeding releases 
> continue on the trunk. 
Usually, yes. In a perfect world, the code would not require any fixes or
fine-tuning after being released to QA, so the branch would never get used.
In real life, though, that tends to be how it works.


> Is this concept incorrect or is there a difference between 
> within cvs between a
> private branch and a non-import branch?

I think maybe there's a confusion in terminology here. CVS itself does not
have any concept of a "private branch". As far as CVS is concerned, the
private branch I described and the release branch you described are both
branches, and CVS treats them exactly the same. What distinguishes the two
types of branches is _how_ they are used.

By convention (the one I'm suggesting, I don't know if this is a standard
practise or not), anything checked into a branch that is designated as a
private branch is not considered a candidate for release or for builds.
Anything checked into a release branch is a candidate.

Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (
Columnist, C/C++ Users Journal (

reply via email to

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