Getting Started With Subversion

"Source control is one of those things that one rarely notices they need until it's far too late, usually when you accidentally delete part of your source tree instead of simply moving it to a different location, or when you make a set of complex changes that leave you worse off than were you started (but you can't go back). A source control system solves these problems by keeping copies of each revision of a set of files on a server, while giving you access to a local copy of those files to make changes on. Good source control systems allow multiple people to modify a single file at once, and will try to automatically merge changes between differing sets of modifications. A good source control system will also let you browse the history of a file or set of files (allowing you to "go back in time") and allow you to have acccess to your code from as many systems as you like. Subversion is one of those good source control systems."

http://dojo.jot.com/Getting%20Started%20With%20Subversion

Version Control for Designers

"Version control

* allows programmers to easily communicate their work to other programmers
* allows a team to share code
* maintains separate “production” versions of code that are always deployable
* allows simultaneous development of different features on the same codebase
* keeps track of all old versions of files
* prevents work being overwritten"

http://hoth.entp.com/output/git_for_designers.html

Subversion For Writers

"This article was inspired by a question asked by a user on the WriteRoom Forum. This person was asking about facilities for working with multiple drafts of a work in progress; a process he was currently doing manually by saving his work with a new timestamp in the files’ names every time. What a lot of work! Clearly a job for a lazy geek to step in and show how it can be done easily!"

http://strangenoises.org/subversion-for-writers/

A Visual Guide to Version Control

"You’ve probably cooked up your own version control system without realizing it had such a geeky name. Got any files like this? (Not these exact ones I hope).

* KalidAzadResumeOct2006.doc
* KalidAzadResumeMar2007.doc
* instacalc-logo3.png
* instacalc-logo4.png
* logo-old.png

It’s why we use “Save As”. You want the new file without obliterating the old one. It’s a common problem, and solutions are usually like this:

* Make a single backup copy (Document.old.txt).
* If we’re clever, we add a version number or date: Document_V1.txt, DocumentMarch2007.txt
* We may even use a shared folder so other people can see and edit files without sending them over email. Hopefully they relabel the file after they save it."

http://betterexplained.com/articles/a-visual-guide-to-version-control/

Beanstalk - Hosted Subversion

"Beanstalk is a hosted Subversion system, making it easy to setup, browse, and track Subversion. Beanstalk has built-in integration with your favorite tools such as Basecamp, FogBugz, Campfire and more"

http://www.beanstalkapp.com/