December 2011
Beginner
176 pages
3h 54m
English
Because we’ve been doing pretty rapid development of a complex system in a multiteam scenario, we’ve had plenty of challenges to deal with. One lesson we’ve learned is that we should have gotten our version control system in shape before we scaled from thirty to sixty people. For long periods our version control system had seriously broken trunks and branches. In fact, at one point the teams even set up a dedicated Kanban board for all the problems in the trunk!

To avoid this problem in the future, we decided to implement the mainline model, a stable-trunk pattern described in my article “Agile Version Control ...
Read now
Unlock full access