Which is best practice? Adding per solution or per project?

[Greg Ward]

On Fri, Nov 26, 2010 at 3:44 PM, martinortiz <martinortiz at optonline.net> wrote:
> Which is best to do? I have about 10 projects, that are all part of the same
> visual studio solution. My solution is the main directory, lets call it Root
> All the other projects from solution, are in this directory. What I did was
> created a repository on the Root folder. This works, but is this a good
> idea? Or should I create a repository on a per project level? I have an
> Mercurial plugin for VS, so for the Root repository, checking stuff in
> etc...is easy. What would happen if I created repositories on a per project
> level? Would I only be allowed to load and manage projects with Mercurial
> correctly when I loaded the whole solution?

The answer to all high-level workflow questions is the same: "It
depends on your circumstances".

I don't think the IDE matters all that much.  What matters are your
policies and procedures for branching and releasing.  In particular,
if all of your projects are branched and released at the same time, on
the same schedule, according to the same policies, then there is no
problem putting them in the same repository.  But if they are
maintained by separate developers or separate teams, and follow
different release schedules and branching policies, then they should
be in separate Mercurial repositories.

Greg