This is the second post in a series about source code management. If you haven’t already read the beginning of the story you can find it here.
We’d realised that we’d outgrown our system of one-developer-per-customer and ad-hoc communication between teams about ongoing changes to objects. We needed some more structure and somewhere safe to keep previous versions of objects.
We…
Continue Reading james’s Article on their blog
Adopting TFVC – James Pearson
Blog Syndicated with james’s Permission