Agile version control with multiple teams
Taking the pain out of branching & merging
Here's a paper describing a strategy for version control with multiple teams in an agile environment. It is hosted on InfoQ. Enjoy!
- Online version (best for reading read on screen)
- PDF version (best for printing)
- Single-page summary in print-friendly format.
Re: Agile version control with multiple teams
This article is now up on InfoQ!
http://www.infoq.com/articles/agile-version-control
Re: Agile version control with multiple teams
Thank you for your work! You saved huge amount of time for our team =) We are using some mix-process (SCRUM & XP) and now going to adapt your ideas from "SCRUM and XP from the trenches". Also we had troubles with agile versioning - the same troubles as you describe =) Wonderful work, thank you :) We are going to cure mergephobia in our team ;)
Re: Agile version control with multiple teams
Re Perforce, it doesn't make sparse branching particularly easy, so I wouldn't bother (unless you have huge branches and a massive repository when it might be worth investigating).
Perforce handles branching and integration very well - Laura Wingerd's work reference above is based on her experience as a VP at Perforce. Her book is well worth reading!



