Yes, sorry I will describe the process.
We are setup with one trunk that the developers use to
check in (unit tested) their changed code. A UAT TAG
is created each day to migrate the changes to UAT.
The issue is I do not know how we are going to get the
code that has been approved in UAT to QA because the
TAG that was created for QA contains approved and
unapproved code. I thought that a QA branch could be
used to handle the changes moving forward. Is there a
way to mark the approved code so that it can be
checked out for migration to QA and PROD?
--- Andy Levy <firstname.lastname@example.org> wrote:
> On 6/5/06, Steven Lavallee <email@example.com>
> > Thank you for the information.
> > I do not understand how the code migrates to
> > Production after it has been approved in QA. Not
> > of the code in a TAG for QA is approved. We have
> > weekly migrations to Production how do pieces of
> > TAG get moved to Production?
> How things migrate really is dictated by your team &
> process. SVN is
> just a tool that holds your project artifacts. It
> doesn't enforce
> anything that you don't set it up to (via hook
> scripts and/or process
> Only tag what's supposed to move to production. If
> you can't isolate
> those elements, then you need to re-evaluate your
> strategy, your
> source layout, or your choice of SCM tools. Or,
> create branches from
> 100% approved versions and ONLY change items that
> can be approved
> (then tagged & released) within a week. But that
> will quickly become
> a branch-management nightmare.
> Perhaps if you could describe for us your full
> process, someone could
> propose a more workable solution. Giving details in
> drips and drabs
> will just prolong the confusion, and may send you
> down the wrong path.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jun 6 04:56:40 2006