On 7/12/05, Simon Lin <noisebar@yahoo.ca> wrote:
> Hi,
>
> I'm looking for some help on moving a tag which we do a lot in CVS but
> haven't figured out a way to do in Subversion. The scenario is as
> following:
>
> 1. We code freeze iteration 1 and release it to QA. That is, we tag the
> head as 'iteration_1'.
> 2. We continue development in head for iteration 2 while QA is testing.
> 3. We make some change in head that is for iteration 2 but definitely
> not for iteration 1.
> 4. QA find a bug in iteration 1.
> 5. We fix the bug. The change doesn't rely on the change we made in step 3.
> 6. Now we want move the tag 'iteration_1' on the file that we changed in
> step 5 to the head version of the file so that we can check out tag
> 'iteration_1' and release it to QA again.
>
> I hope I'm not confusing anybody. This is something we do in every
> iteration. We hope we can do the same thing in Subversion.
>
What your describing is much simpler in svn than in CVS, but what you
need is a paradigm shift. Your current workflow uses tags rather than
a branch since branching in CVS is a pain. In svn what you would do is
create an iteration1 branch rather than a tag. Tags in svn parlance
are read only, whereas branches are not.
Now the way you would handle the bug fixes will vary according to your
development philosophy. In subversion itself all development occurs on
trunk, and then changes are merged selectively onto the release
branches. It might be more natural for your group to do the bug fixes
on the branch and then merge those changes back to the trunk if they
are needed (i.e the bug has not already been fixed there due to other
changes).
Either way viewing iteration1 as a branch rather than a tag will make
applying svn to it more natural.
Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 12 17:57:16 2005