Hi Andy,
I have over 100 "modules" and I have organised them as projects based on
how they will be released.
All modules that need to be compiled and released together constitute a
project. This allows for easier tagging, branching & merging. I have at
the moment just under 100 "projects".
If a module is shared and could be compiled and release independently,
then it constitutes a project by it self.
Thanks
Lakshman
-----Original Message-----
From: Andy Levy [mailto:andy.levy@gmail.com]
Sent: Friday, 28 April 2006 6:33 AM
To: bedouglas@earthlink.net
Cc: Ron; users@subversion.tigris.org
Subject: Re: Large Repository .vs Many Smaller ones..
On 4/27/06, bruce <bedouglas@earthlink.net> wrote:
> Good point...
>
> if all goes well, the repository will have upwards of 400-500 small
> projects, each of which would only have a few files... if each change
to a
> file, would cause the revision number to jump, i could have huge gaps
in the
> revisions numbers of a file between consecutive changes in a given
file.
This is only significant if you apply an artifical importance to
revision numbers. Revision numbers aren't meant to be used as
"checkpoints" - use tags for that. Don't get hung up on revision
numbers having real meaning.
> might have to revisit the large .vs small issue. although, from a
management
> perspective, it would be far easier to have one large repository.
As opposed to 400-500 smaller ones? Definitely. If you can break
those projects into logical units (by workgroup, company division,
platform, something like that) maybe 4 or 5 repositories would make
sense.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 28 03:12:35 2006