Subversion is an open source project used to automate the version control process for documents. OK, that is a simple statement, but what does it mean and how does one implement it? The answer is that there are countless ways to implement it, so I will give you just one; how I did it.
I am a lone developer with no IT department and I have very little extra time, so I have chosen a very simple approach. My objectives are to keep track of changes to the software for each of my clients as well as safely storing the files. Note: I live in the Windows eco-system, so this is a Microsoft-centric solution.
Subversion (abbreviated here as SVN) is a server-client architecture. On the server side I use a computer with the VisualSVN server installed that uses the folder c:\repositories for all of the file repositories. This folder is synced with Microsoft’s Live Mesh up to SkyDrive. The net effect is that when I check a file into the repository I know that I have a local copy as well as a copy safely tucked away in the cloud (SkyDrive).