Source Control Saves Lives
Lorna Mitchell Source Control Saves Lives BarCamp Leeds What is Source Control? Central filestore Change history Audit trail by user
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Source Control Solutions Subversion CVS GIT Bazaar Visual Source Safe
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Working With Subversion Code is held in a central repository Developer checks out code to their own development area Developer makes changes to code Changes are committed back to repository, with a comment
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Subversion And Teams Changes made to repository during developer's change – update before commit Changes made to same files – subversion will merge Changes made to same lines in same files – a collision New files of same name - obstruction
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Subversion For One Central backup location Incremental versioning Change history of copied/merged code Tagging of key moments
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Subversion For More Than One Central current version always available Blame/Praise function for all changes Branching for major changes/new versions
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Subversion Tricks Diff between any two files/revisions Change history with name/date/files/comment Patch between projects/branches and track these Recover deleted files and rollback mistakes
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Subversion Access Methods SVN command-line HTTP SVN+SSH Client tools/plugins
Lorna Mitchell Source Control Saves Lives BarCamp Leeds Subversion Resources Documentation at Red Bean Book, an online reference Pragmatic Version Control Using Subversion, Mike Mason
Lorna Mitchell