How should we organize svn?
We can have one trunk/branch/tag and under it a bunch of projects.
We can have multiple top-level things, each having (optionally)
trunk/branch/tag and under those a bunch of projects.
I say optionally, because I see projects that have sandbox as one of
the
To me, the SDK has a meaning of adding tools, examples, etc. to a core
thing. Using it as a top-level collection name for the various
framework implementations seems a bit off.
I think our big code bases (Java, C++, maybe others in the future - e.g.
C#, javaScript) could go into their own
To me, the SDK has a meaning of adding tools, examples, etc. to a core
thing. Using it as a top-level collection name for the various
framework implementations seems a bit off.
I agree with that meaning of SDK, but seem to have come to the
opposite conclusion. :) What I was proposing as
On 11/9/06, Marshall Schor [EMAIL PROTECTED] wrote:
snip/
So branching and tagging aren't very straightforward in that scenario.
I'm not sure this is true. Yes, creating a branch or tag is copying the
whole project, but it is a lazy copy. So, yes, it would collect a bunch of
things that
