Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If we want to have code reviews before a developer delivers his work, then can you suggest whether multi stream project { i.e., each developer create his own stream and view and later deliver to single stream.} or single stream { i.e., all developers work on same stream } which is advisable.

share|improve this question

migrated from Jul 12 '11 at 14:55

This question came from our site for professional and enthusiast programmers.

Multi-stream project is fine, and provide natural isolation through branching.

However, it doesn't scale well and force developer to multiple merges if they need to get the work of their colleagues.
So if they can develop in isolation and don't depend heavily and regularly on the work of their peers, multi-stream is fine.

That being said, I prefer this model when each stream represents a development effort, and not a developer (even though you still can match one developer to said development effort): see this answer for more.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.