On 11/20/2006 10:38 AM, Phyrefly wrote:
>> For example: You create the label as above, then continue work on the
>> trunk in preparation for version 2. A user finds a bug, so at that
>> point you create a branch from trunk -r"release1.5", and fix the bug,
>> releasing it as something you want to call "release1.6". But that's not
>> enough! If "release1.6" just contains the revision number (54321 at this
>> point), it won't tell you that it's not from the trunk, it's from the
>> branch.
>
> The label isn't repo-wide, it's per-file, so the only files labelled
> "release 1.6" are in the branch. No problem here.
Sorry, I misunderstood what you meant by a label. I think this gets
back to what someone else said: there needs to be a particular proposal
in place to discuss. When everyone says "label" but means different
things, confusions like this will happen.
Duncan Murdoch
>> You should have branched at the time you decided you would fix bugs on
>> the release. Then you should tag each release by copying it somewhere,
>> so you can find releases in a known place.
>
> That's how I'm forced to work now, but that's not a way I can teach
> people to use the system. Let's not start that again.
>
>> Tagging is exactly equivalent: but instead of plugging a rev number in,
>> you plug a URL in.
>
> And therefore it's not equivalent, and requires changing a part of the
> command that I don't change for anything else.
>
>> Since in the general case it is *impossible* to
>> update to a particular release (e.g. you can't update trunk to
>> "release1.6" in the example above), you have to switch to it, and you
>> might as be consistent and *always* use the same way to switch to a
>> particular release.
>
> This is the first argument against the efficiency of labelling that
> I've heard yet. And it does make a lot of sense, in some
> environments.
>
> In the environment I work in, we don't ever use branches (for various
> reasons) - if I needed to fix a bug in 1.5, I'd fix it on trunk, and
> it would be fixed in the next stable version. Those versions are
> never far enough apart, timewise, to be worth branching for an
> intermediate release. So I suppose one of the major differences is
> that in my environment, the implementation of tagging is forcing me to
> use branching, even though the only thing I will ever use it for is
> tagging. In an environment where you use branches anyway, getting
> people to use tagging as implemented would make more sense.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 20 21:23:22 2006