Summary
Modern source-control systems provide powerful tools that make it easy to create branches in source code.
1
Martin Fowler recently released a post in Branching Patterns, which outlines how he uses them to think about git-flow, GitHub Flow, and Trunk-Based Development.
2
He also shared his thoughts on the differences between feature branches and continuous integration, and asked for motivational beverages for the follow-up article.
2
Finally, he concluded that a single maturity branch does not make sense in the context of multiple releases being live.
2
According to
Summary
Modern source-control systems provide powerful tools that make it easy to create branches in source code. But eventually these branches have to be merged back together, and many teams spend an inordinate amount of time coping with their tangled thicket of branches.
Patterns for Managing Source Code Branches
martinfowler.com
Paul Hammant provides more details of using Branch-by-Abstraction, particularly as an alternative to using version-control branching.
BranchByAbstraction
martinfowler.com
Modern source-control systems provide powerful tools that make it easy to create branches in source code. But eventually these branches have to be merged back ...
version control
martinfowler.com
Here I explore the wider context, showing how continuous integration fits into the broader topic of branching. Branching is easy, merging is harder - and the ...
Continuous Integration
martinfowler.com
Subversion encourages a simple central repository model, discouraging large scale branching. In an environment that's using Continuous Integration , which is ...
VersionControlTools
martinfowler.com
