Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
> From: Tony Hoyle > In fact it's difficult > to imagine a scenario where there would be multiple ones... if your > developers depend on each other they must be on the same branch. If > your developers are working on completely independent code then they > might as well be in the same branch as they won't conflict. Not all institutions deploying a revision control system trust their developers, and some put a buffer between the developers and HEAD. Example: the Bodington project. Several institutions develop on Bod, often funded by research grants. The developers don't necessarily have commit privileges to HEAD, as policy requires that the code is tested before being merged and that's done by a separate merge team. Typically, a branch is created for each project, appropriate developers are granted commit access, and then it's tested and potentially merged in when they declare it's complete. - Peter