Version Control Tips
Continue Reading February 6th, 2009 Krister Schwertfuehrer
I’m sure you’re saying “Who needs this in this day and age?” Well, as recently as last year, I encountered a development team that was still not using ANY version control. I couldn’t believe it!
Throughout my career I’ve encountered several different version control philosophies, from using *.BAK files on a production server (maybe with a date/timestamp added to the filename to know when the change was made) to systems where automated builds let developers know within minutes whether or not their latest check-in broke something (and most everything in between).
This article contains the nuggets that I’ve gleaned from my experiences and from reading various other items. It is not intended to be a be-all, end-all, but a starting point (perhaps just a starting point for discussions… and that’s why I’ve decided to write this). Searching for “Version Control Best Practice” in Google yields some 20 million results. So, I’d at least like to put this in a place where I can point people to when I want to explain to them about Version Control Practices.
