Which is best practice? Adding per solution or per project?
martinortiz
martinortiz at optonline.net
Mon Nov 29 17:54:44 CST 2010
Yes, I was wondering if size would be an issue.
The projects are not large in this case though, if they were, I would
probably go the other route.
-------Original Message-------
From: Stanimir Stamenkov-3 [via Mercurial]
Date: 11/29/2010 5:40:21 PM
To: martinortiz
Subject: Re: Which is best practice? Adding per solution or per project?
Mon, 29 Nov 2010 17:21:21 -0500, /Greg Ward/:
> 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.
I guess it also depends on the size of the modules/projects. Even if
they get branched and released at the same time, it may make sense to
create separate repositories for them, and then probably use
subrepositories to group them together.
> 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.
--
Stanimir
_______________________________________________
Mercurial mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial
View message @ http://mercurial.808500.n3.nabble
com/Which-is-best-practice-Adding-per-solution-or-per-project-tp1974680p19894
0.html
To unsubscribe from Which is best practice? Adding per solution or per
project?, click here.
--
View this message in context: http://mercurial.808500.n3.nabble.com/Which-is-best-practice-Adding-per-solution-or-per-project-tp1974680p1989705.html
Sent from the General mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20101129/4a108be8/attachment.htm>
More information about the Mercurial
mailing list