Home/ Questions/Q 289489
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T05:54:42+00:00

I was reading this post about branch per feature and this one too and

  • 0

I was reading this post about “branch per feature” and this one too and found myself wondering how many people out there are using this concept? I am all for continuous integration and tagging each check in. And at the end of an iteration I create a special tag set to identify the sprints result. I have never needed to take it further by creating a special branch for each features development.

Question: Does anyone branch their code for the development of each feature in their code base? If so, why do you do that and what are the benefits that you have seen from this process? Do the non-process oriented developers on your team buy off on this approach?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I haven’t heard of such a thing. Seems like an overuse of branching to me. I guess it depends on what we mean by the word “feature”. Is it a use case? A user story? An entire iteration?

    Branches imply parallel development. If you aren’t developing in parallel, why branch?

    Some good SCM references from our host, Jeff Atwood:

    1. Eric Sink
    2. Branching and Merging Primer

    And, of course, the SVN red bean book:

    http://svnbook.red-bean.com/

    I also like what “Pragmatic Version Control” has to say about branching and tagging.

    • 0