> So the official directory layout for Avalon is:
You realize that this is bad, right?
> /avalon
> /branches
> /releases
> /trunk
That means that the thing being versioned is /avalon, at the root. That is
not what you want. You want to organize by versionable/releaseable
component, and then have trunk/, tags/ and branches/ below each. These
"ttb" directories are the convention by which you manage versioning:
trunk/ - a directory containing the main development tree
tags/ - a directory containing DIRECTORIES, each of which
is a copy of the development tree.
branches/ - a directory containing DIRECTORIES, each of which
is a copy of the development tree.
Notice that tags and branches are given the same description. Yes, I did
that on purpose. Here is the difference: if you change something after you
make it a copy, it is a branch. If you don't, it is a tag. These things
are nothing more than naming conventions using lightweight copies. Even the
names "trunk", "tags" and "branches" are just conventions. But they are
good conventions.
If we are developing the foo widget in trunk, and I want to create a branch
for some exploration, I would COPY foo/trunk to foo/branches/myplaypen, do
some work there, and eventually merge my changes back into foo/trunk. If I
want to checkout Phoenix version XYZ, I'd checkout /avalon/phoenix/tags/XYZ.
Does this make sense to you now?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
