[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN: Branches Questions

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-06-06 04:40:51 CEST

On 6/5/06, Steven Lavallee <stvcinlav@yahoo.com> wrote:
> Thank you for the information.
> I do not understand how the code migrates to
> Production after it has been approved in QA. Not all
> of the code in a TAG for QA is approved. We have
> weekly migrations to Production how do pieces of the
> 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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 6 04:42:20 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.