[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 03:11) wrote:

> we could move all FW_3 apps under the FW_3 horde in the repository, 
> so that they are useable as-is. Then we could re-engineer HEAD to 
> simply work while expecting things to be side-by-side. That way we 
> get reasonable behavior for the (not so huge) set of FW_3 apps, and 
> can break BC for HEAD and have a nicer structure overall, period.

But that would meen that anybody checking out the horde module from FW_3
would get all apps checked out too, correct?

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.