[Top][All Lists]

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

General process with multiple developers

From: kurt . milligan
Subject: General process with multiple developers
Date: 25 Aug 2005 12:10:12 -0700
User-agent: G2/0.2

Hi All

Been using CVS for a long time on very small (read: single developer)
projects, but now want to start using it with multiple developers, and
have a question. I'm sure this has probably been asked before, so if
someone can point me in the right direction, it would be greatly

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


reply via email to

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