On 12/19/06, Thomas Hemmer <themmer@go-engineering.de> wrote:
> Bill,
>
> I personally would prefer a structure like
>
[... one /tags for all apps]
>
> assuming your app1, app2, ..., appN together form one deployable
> product.
That would be much nicer, but unfortunately they're all on separate
release schedules. We talked about doing that, but we're worried that
it's too space inefficient, and deleting all the unnecessary apps
every time would be error-prone and just kind of annoying.
>
> Another scenario could be that app1, app2, ..., appN each are separate
> products; in this case I would propose the following scheme:
>
> /project.root
> /branches
> /tags
> /app1
> /1.0
> /app
> /common
> /1.1
> /app
> /common
> ...
> /app2
> /1.0
> /app
> /common
> /1.1
> /app
> /common
> ...
> /trunk
> /app1
> /app2
> /Common
>
Why have the tags at the top-level? It seems to me, semantically, that
the tags are of an application, and thus should be in a subfolder of
its application's parent folder.
On the other hand, that structure does seem to make branching match
more simply with what we're doing.
Thanks
Bill Mill
bill.mill at gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 19 20:18:46 2006