Databases
StackOverflow2013
Postsdbo
POUsing Mercurial in a Large Organization
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Mercurial in a Large Organization
    text
    copied!<p>I've been using Mercurial for my own personal projects for a while, and I love it. My employer is considering a switch from CVS to SVN, but I'm wondering whether I should push for Mercurial (or some other DVCS) instead.</p> <p>One wrinkle with Mercurial is that it seems to be designed around the idea of having a single repository per "project". In this organization, there are dozens of different executables, DLLs, and other components in the current CVS repository, hierarchically organized. There are a lot of generic reusable components, but also some customer-specific components, and customer-specific configurations. The current build procedures generally get some set of subtrees out of the CVS repository.</p> <p>If we move from CVS to Mercurial, what is the best way to organize the repository/repositories? Should we have one huge Mercurial repository containing everything? If not, how fine-grained should the smaller repositories be? I think people will find it very annoying if they have to pull and push updates from a lot of different places, but they will also find it annoying if they have to pull/push the entire company codebase.</p> <p>Anybody have experience with this, or advice?</p> <hr> <p>Related questions:</p> <ul> <li><a href="https://stackoverflow.com/questions/2383826/git-based-source-control-in-the-enterprise-suggested-tools-and-practices">Git-Based Source Control in the Enterprise: Suggested Tools and Practices?</a></li> <li><a href="https://stackoverflow.com/questions/2476356/distributed-version-control-for-huge-projects-is-it-feasible">Distributed version control for HUGE projects - is it feasible?</a></li> </ul>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload