[Tickets #5284] Re: Move to subversion for Horde code repository

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5284
-----------------------------------------------------------------------
 Ticket             | 5284
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | Move to subversion for Horde code repository
 Queue              | Horde.org Servers
 Type               | Enhancement
 State              | Assigned
 Priority           | 2. Medium
 Owners             | Horde Developers
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2007-11-05 09:45) wrote:

>> After taking a look at the current SVN repository, I changed my mind
>> and think we should setup separate modules for each Horde app. Having
>> all tags and branches for all horde modules ever in branches/ and
>> tags/ looks really cluttered. I think it's worth not being able to
>> svn mv between horde modules for the benefit of a cleaner layout.
>
> We could still svn mv/copy between them, unless we really made them 
> completely separate repositories. There is nothing hardcoded in 
> subversion about trunk/tags/etc - it's just a convention. We could to 
> a top-level list of modules with their own trunk, tags, branches 
> dirs, or we could do subdirs inside the /tags and /branches dirs just 
> like we have inside /trunk.

I would prefer top-level modules, then trunk/tags/branches. But we should
make sure first that Chora works fine with that. :)