If you are working on project with a team of developers, then revision control is necessary, period. Even developers working solo on a project will find that using a revision control system provides many benefits. Revision control systems have been around for over a decade, and Apache Subversion (SVN) has been the most popular system for much of that time.
How does revision control work?
Revision control is the management of changes to the files of a development project. Changes are usually identified by a number or letter code, termed the "revision number", "revision level", or simply "revision". For example, an initial set of files is "revision 1". When the first change is made, the resulting set is "revision 2", and so on. Each revision is associated with a timestamp and the person making the change. Revisions can be compared, restored, and with some types of files, merged.
How does a Centralized Revision Control System work?
Centralized Revision Control Systems (CRCS) use a centralized model where all the revision control functions take place on a shared server. If two developers try to change the same file at the same time, without some method of managing access the developers may end up overwriting each others' work. Centralized revision control systems solve this problem in one of two different "source management models": file locking and version merging.
What's good about Subversion?
The biggest asset that Subversion currently has is it's popularity; it's been around for a decade, so you can find lots of developers that are already familiar with it. Subversion was created by CollabNet Inc. in 2000 and is now a top-level Apache project being built and used by a global community of contributors. While the Subversion project does not include an official graphical user interface (GUI) for use with Subversion, third parties have developed a number of different GUIs, along with a wide variety of additional ancillary software.
Does this meetup need any volunteers?
We currently have a presenter for this meetup, but are still looking for co-presenters with experience in the subject to assist, as well as volunteers to help with various aspects of the meeting (like signing attendees in and videotaping the presentation). The meetup will be presented by Chris Baril, who holds a Computer Science B.S. degree from the University of British Columbia and has been developing websites since the late 90s. For more information visit chrisbaril.com
Who should attend?
INTENDED AUDIENCE: Front-end and back-end developers
DIFFICULTY LEVEL: Beginner/Intermediate
Where should I start?