Difference between revisions of "How to Avoid Branching"
From CitconWiki
Jump to navigationJump to searchPaulJulius (talk | contribs) |
PaulJulius (talk | contribs) |
||
| Line 12: | Line 12: | ||
Team members need to have the skills to make the changes | Team members need to have the skills to make the changes | ||
| + | |||
| + | The mindset gets in the way of people making a change from one monolithic build | ||
| + | |||
| + | I want refactor mercilessly | ||
| + | |||
| + | I want to release rapidly | ||
| + | |||
| + | 100s of developers, with a big legacy codebases | ||
| + | |||
Revision as of 01:21, 18 May 2019
Problem:
Best practices for Trunk-Based Development
Goal is Continuous Integration
Really we want Faster Feedback
Complications:
In monolithic codebases, it's hard to make quick changes
Team members need to have the skills to make the changes
The mindset gets in the way of people making a change from one monolithic build
I want refactor mercilessly
I want to release rapidly
100s of developers, with a big legacy codebases
Potential Solutions:
Baz
