On Fri, Nov 16, 2001 at 10:05:29AM -0800, Bruce Atherton wrote:
> At 09:22 AM 11/16/2001 -0500, Kevin Pilch-Bisson wrote:
>...
> >Now maybe the way to do this is to just always branch/tag the whole project
> >(since it doesn't take up any extra space/time).
>
> This is a very interesting idea, but I can see a few problems with it.
>
> First of all, it assumes that everything in your working copy is ready to
> be promoted. This is often not the case, and will almost certainly result
> in developers getting very confused about files "mysteriously" getting tagged.
>
> Secondly, I don't think it would play well with other developers changes.
> You would essentially be saying that all files in your working copy are
> ready to be promoted, including those being worked on by somebody else.
> They might not be too happy about that.
In your particular scenario, I could see the following tree layout:
/
trunk/
integ/
bruce/
john/
jane/
integ/ is a copy of trunk/. Whenever you want to release a file(s) for
integration, you copy it over to integ/bruce/ and commit that change. Your
integration team merges changes from the integ/ area into trunk/
Does that work the same as today? Nope. Does it make sense for your
particular scenario? Can't really say. But it is a first pass. I'm sure you
can refine it.
Basically: to tag individual files, just copy them into a "tag area".
I think about the only real conclusion to this thread is to say that SVN has
its definition of tagging. Let's see how people will work with that model,
what kinds of tools people will ask for and develop, and we can go from
there. The copy model is a lot better than CVS's model for a number of
reasons, but is quite different. Maybe it will fall down in a particular
scenario where CVS succeeds. Oh well... we rock in so many other areas that
I'm not too concerned :-)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:48 2006