On 7/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: bdubbs
> Date: 2007-07-24 13:11:06 -0600 (Tue, 24 Jul 2007)
> New Revision: 8239
>
> Added:
>    branches/6.3/
> Removed:
>    tags/6.3-rc1/
> Log:
> Move tags/6.3-rc1 from tags to branches/6.3
>
> Copied: branches/6.3 (from rev 8238, tags/6.3-rc1)

Sorry to keep pestering, but you normally want both to be there. Stuff
in tags is supposed to be static. The idea being that you can use
6.3-rc1 as a benchmark to compare the next rc or release. During this
phase, we would have

trunk
branches/6.3
tags/6.3-rc1

trunk moves forward, diverging from branches/6.3 as new things are
merged in. Things get fixed in branches/6.3 (and possibly in trunk if
it still applies). Eventually, we have rc2. Now we have

trunk
branches/6.3
tags/6.3-rc{1,2}

That's convenient since now you have a copy of the tree from rc1 and
rc2. With SVN, this is not enforced, and it's also bloated as a full
copy is done, but it's still a good idea in the meantime. That's why
the branches/tags functionality is there.

When 6.3 final is released, we can probably remove the -rc* tags and
maybe the 6.3 branch if we don't expect to backport any more fixes.

Do you agree?

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to