RE: Branching strategy - Feature vs Release

On Wed, 2006-11-08 at 17:42, Richard Gundersen wrote:

> >
> >I can see an advantage for stable-trunk where you permit public access
> >to the repository so everyone doesn't have to know about the purpose
> >of each branch. Otherwise the trunk may be more valuable for new
> >development work that hasn't reached the QA stage yet.
> >
> I disagree. I think having a stable trunk, that mimics the production copy
> of a system is very important.

Important in what way? What do you see different about making a
branch from the trunk first, testing and perhaps making changes that
shouldn't appear in the trunk (you'd merge them if you wanted them
there) on the branch and tagging the release from there? You end
up with a tag matching each production release either way. Forcing
it all to exist on the trunk serializes things unnecessarily and makes
you back out changes that you knew were added temporarily for a
specific release only.

> I still don't see any compelling reason to ditch the feature branch approach
> for the release branch approach.

The main reason is to let concurrent new/untested development continue
to happen on the trunk with all developers updating to each other's work
as frequently as possible so they aren't making incompatible changes.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org