[Top][All Lists]

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

Re: General process with multiple developers

From: Todd Denniston
Subject: Re: General process with multiple developers
Date: Thu, 25 Aug 2005 16:56:39 -0500

address@hidden wrote:
> Hi All
> Let's say you have a good-sized CVS project, and several developers.
> Every developer has their own sandbox.
> One group of developers is working on a section of the project (which
> cannot, for various reasons, be its own project), and they need to be
> able to "share" their changes related to that section of the project
> with other members of the same group, but not everyone else. Normally
> developer A would commit their changes, and then developer B would
> simply do an update. However, we don't necessarily want developer C, or
> the QA sandbox for example, to "see" those changes (get them on an
> update) until the group says they are ready. Any standard practices on
> this?
> -Kurt

Sounds like what you want to do is put different groups on different
branches of the sub project.

here is a cut and past from a message I sent in 2003 on a similar subject,
note the msg00771 thread link it talks a little about having approved bug
fix and QA branches:

Brad Appleton and others "Branching Patterns for Parallel Software
has helped me a lot. He also has a lot of SCM links on the page. (Note: the
page has

there are some books listed off of:

[ed. these are now somewhere off of :

David Thornley has some practical help for cvs users.

try following the thread in:
there is some advice and links to resources there.

Also searching for books or resources or branching and scm may turn up
something  in the archives.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

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