As the subject states, I have a question about what I think may be an
unconventional repo layout, and what everyone here might think about it. It
revolves around the notion that there's a product suite, with multiple
products below it, however, there are many(> 50) "modules" that we have
created to interact with various third parties. Rather than have these
modules all in the main product suite line, and since they can change
anytime, and need updating, I was thinking about putting them in a
sub-directory under the product suite, and then within each module name,
creating a new branches/, tags/, trunk/ structure. Below is a diagram of
what I'm trying to achieve.
ProductSuite/
branches/
tags/
trunk/
Product1/
Product2/
Modules/
Module1/
branches/
tags/
trunk/
Module2/
branches/
tags/
trunk/
I thought that this might be good, because I can then easily tag or branch
the whole suite for major work, or whole releases. At the same time I can
just update a given module, or work on a whole new implementation of it
without taking the whole suite along for the ride.
Hopefully I explained well enough what I'm trying to achieve.
Thanks,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 17:57:57 2004