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

Re: Branched and non-branched work flows?

From: David Weintraub <qazwart_at_gmail.com>
Date: Mon, 1 Jun 2009 15:40:15 -0400

On Mon, Jun 1, 2009 at 3:11 PM, Bob Archer <bob.archer_at_amsi.com> wrote:

> That's pretty close to how we do it to. But, we build, test and release
> from trunk. We don't allow v+1 to be checked into trunk until the release is
> gold. (If there is need we create a temp branch for v+1, but this doesn't
> happen often.)

The whole point of creating a branch for the "V" release is so you can check
in code on the trunk for your V+1 release without messing up your "V"
release. If you're going to implement a code freeze anyway, then don't
bother with creating a "V" branch.

Creating a "V" branch allows you to put a code freeze in place for Release
"V", but allows you to continue your work on "V+1". Branch on the code
freeze and do your releases off the branch.

By the way, if a customer finds a bug in Release "V", and you need to create
a Release V.1, there's no need to create another branch for the V.1 patch
release. You're not holding up any development by not having a branch.

David Weintraub
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-01 21:41:14 CEST

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