Skip to content

Instantly share code, notes, and snippets.

@tdpauw

tdpauw/devoxxbe-2017-proposal-feature-branching-is-evil

Last active June 22, 2017 13:10
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tdpauw/ca9d1538f4060a73305525f6131e0b1e to your computer and use it in GitHub Desktop.
Save tdpauw/ca9d1538f4060a73305525f6131e0b1e to your computer and use it in GitHub Desktop.
Download ZIP
Feature Branching is Evil abstract for Devoxx BE 2017
Raw
devoxxbe-2017-proposal-feature-branching-is-evil
Feature branching is gaining in popularity due to the rise of Distributed Version Control Systems like Git and Mercurial.
Mostly because proponents of DVCSs rely on feature branching to sell DVCS. And because of the success of branching models like
GitFlow and GitHub Flow.
Like all powerful tools, there are many ways you can use DVCSs, and not all of them are good. Although the creation of feature
branches became very easy with DVCSs, it does not mean cheap in the long run. It comes with a certain cost which impacts the
stability and speed of your software delivery process.
During this session we will explore some of the reasons teams are using feature branches, what problems are introduced by
using feature branches and what techniques exist to avoid them all together.
In conclusion we will explore what is evil about feature branching, which is not necessarily the problems they introduce. But
rather the real reasons teams are using them for.
The key takeaway will be an appreciation of a different branching strategy and how it relates to Continuous Integration.
The session’s target audience is anyone using version control systems in a Continuous Integration and Delivery context.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment