Version Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version.
Great article Khalid, and thanks for the link to Eric’s articles, they were pretty good too!
I will be testing the tagging and branching approach you both mention, it will mean I can check out a branch (i.e. previous release) into a new folder…make bug fixes and check it back into the branch and deploy to live server in a more controlled, and traceable way. Then would obviously need to merge bug fixes into my current trunk (development work since last version).
Hi Carlton, thanks for dropping by! Yep, I’m working out my own branching/merging scheme to make it easy to edit/update the live version while still doing new development. Let me know if you have any insights
Hi Mark, thanks for the comment and link – I hadn’t seen that SCM before.
Thanks guys! Not sure what’s happening with the food theme (lifesavers, tasty articles) but I’m happy to oblige
(EDIT: Wow, I had been re-reading the article so many times that I forgot food items were the examples I used! They just became a series of words to me.)
[…] If your developing a project as a group, version control is a necessity. Here is a website which does a better job that I would have at explaining version control: A Visual Guide to Version Control […]
[…] A Visual Guide to Version Control Version Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version. (tags: development guide subversion versioncontrol) […]