October 2016
Intermediate to advanced
480 pages
11h 53m
English
In the previous chapter, we created the automated testing practices to ensure that developers get fast feedback on the quality of their work. This becomes even more important as we increase the number of developers and the number of branches they work on in version control.
The ability to “branch” in version control systems was created primarily to enable developers to work on different parts of the software system in parallel, without the risk of individual developers checking in changes that could destabilize or introduce errors into trunk (sometimes also called master or mainline).†
However, the longer developers are allowed to work in their branches in isolation, the more difficult it becomes ...