What revision control does for you
Revision control allows you to check-point a file as you refine
its contents.
Names (or numbers) on each revision of the
file, created as you make changes, allow you to track differences,
backout of changes that didn't work out, or work on future refinements
while the other engineers are poking along with their changes.
By using the file name and the revision name to
specify the component we are using we eliminate the need to keep
parallel file system heirarchies for each step forward. This
reduces the disk space, number of files, and management costs to
the project team.
What does this mean to me?
Cutting to the core here, revisions with strict locking:
- mark stable points in the developement cycle for each file
- make it easy to track who made what changes
- keep modifications linear
- make a nice log for management