Blair Zajac wrote:
>
> On Mar 24, 2006, at 8:19 AM, Jay Lessik wrote:
>
>> I'm new to subversion so forgive me if this question
>> is newbie-ish...
>>
>> I know that project repository structure has been
>> discussed on this list and I've read a lot of the
>> posts, but I wasn't able to find a clear answer to the
>> question of which of the following is better?
>>
>> repository/
>> projectA/
>> trunk/
>> branches/
>> tags/
>> projectB/
>> trunk/
>> branches/
>> tags/
>>
>> OR...
>>
>> repository/
>> trunk/
>> projectA/
>> projectB/
>> branches/
>> projectA/
>> projectB/
>> tags/
>> projectA/
>> projectB/
>
> I had the later structure for a while at
> http://www.orcaware.com/svn/repos/ but I reorganized the repository to
> the first. It's just odd having your trunk separated from its branches
> and tags that far in the repository, especially when the different
> projects are not related. So I recommend going for the first.
>
> You can see everything related that one project in the project*
> directory without having to go into other locations. It's also nice for
> browsing.
And when $number_of_devs >= 1 and you have teams, and you have authorization in place,
it is usually more natural to go with what is suggested in the manual (the first).
When you are alone - it does not matter that much. And the names ('trunk', 'branches')
are completely suggestive only.
Adding my 2 yen to the discussion ;-)
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 25 03:43:41 2006