branching | TechWell

branching

Branches Choose Continuous Integration over Branching for Faster Feedback

Continuous integration is the best way to get feedback often on the state of your project. Running automated builds and tests after each integration improves reliability and predictability. Consequently, using task and feature branches, while useful in some cases, can be a distraction and delay getting information.

Steve Berczuk's picture
Steve Berczuk
Helpful Tips for Good Branching and Merging in Product Development

Branching and merging are necessary, but they can be minimized to reduce the overhead. In this story, Joe Farah shares several helpful branching and merging tips as well as his simple philosophy of creating a new branch when you need to support the old one.

Joe Farah's picture
Joe Farah
Branching Is Not Just for Version Control

Joe Farah explains to us that a branching strategy is central to a configuration management (CM) plan and that it extends beyond version control. Remember, It's not just the files that need to be organized, it's the entire CM and application lifecycle management (ALM) data repository.

Joe Farah's picture
Joe Farah
Should Agile Teams Minimize Branching?

Steve Berczuk explains that developers are most interested in whether or not an SCM tool is capable of branching, thus allowing more than one related stream of code to evolve in parallel. However, minimizing branching may be the best approach for agile teams.

Steve Berczuk's picture
Steve Berczuk
Variant Management Starts with Design

Joe Farah describes how to not overload your branching with variants so as to permit your customers to dynamically modify the behavior of a software product. Variant management is a CM issue, but it has to be dealt with in the product design first.

Joe Farah's picture
Joe Farah