On Thu, 22 Sep 2005, Bill Dudney wrote:
Well the idea is that people would then be using current/trunk to checkout
instead of just current.
But by definition, what's in branches and tags is not current, so why does
it make sense to include them under 'current'? The structure you described
is exactly what you have without using the 'current' external in the first
place, isn't it?
--
Martin Cooper
TTFN,
-bd-
On Sep 22, 2005, at 12:31 PM, Martin Cooper wrote:
On Thu, 22 Sep 2005, Bill Dudney wrote:
Hi All,
I'd like to propose that we change current to be;
current
/branches
/tags
/trunk
Still all externals but tracking the group of tags & branches that are
common across all the subprojects.
current/trunk -> becomes what we currently call current
current/branches -> currently empty
current/tags -> 1_1_0 with externals to each subproject's 1_1_0 tag
I would recommend against doing that. It would mean that everyone checking
out 'current' would end up with multiple copies of the entire source tree,
which is unlikely to be something that they would want.
Most people are unlikely to want more than one version of the source at any
given time, so I don't see a need to clump together multiple versions in a
single checkout.
--
Martin Cooper
To fix the faces-config.xml bug that's been identified in the 1_1_0
release we can create a branch in current/branches/1_1_0 that uses
externals to the tags for everything but 'build' which would point to the
1_1_0 branch in build (not yet created but I'd be glad to do that).
Thoughts?
TTFN,
-bd-
