Re:Trunk-Based Development
by shawn-butler on Sunday January 29, 2017 @10:58AM
(#13514668)
I think this is the relevant portion for which you are looking:
"We found that having branches or forks with very short
lifetimes (less than a day) before being merged into trunk,
and less than three active branches in total, are important
aspects of continuous delivery, and all contribute to
higher performance. So does merging code into trunk
or master on a daily basis. Teams that don’t have code
freeze periods (when people can’t merge code or pull
requests) also achieve higher performance."
"We found that having branches or forks with very short lifetimes (less than a day) before being merged into trunk, and less than three active branches in total, are important aspects of continuous delivery, and all contribute to higher performance. So does merging code into trunk or master on a daily basis. Teams that don’t have code freeze periods (when people can’t merge code or pull requests) also achieve higher performance."