A Presentation on Version Control System

1. A Presentation on Version Control System Anil K.C. SudeepShrestha NishantBajracharya

2. Let’s Start!!!

3. You Know!!! • Ever saved any documents like?? • Presentation_jan_12.ppt • Presentation_feb_12.ppt • Image.jpg • Image-edit.jpg • Using Save as, so that each time previous document is kept as a back-up? Now, That’s VCS!!!

4. THEN WHY VCS??? • Manipulating one time document is OK. But Software Projects over a network?? NO CHANCE!!! • Many Programmers, many edits = Overwrite + Memory + Chaos ANSWER = VCS

5. VERSION CONTROL SYSTEM • Also known as Revision Control System or Source Control System • Manages the changes of documents, programs, and other information stored as computer files • Commonly used in software development, where a team of people may change the same files

6. A GOOD VCS DOES: • Backup and Restore Files are saved as they are edited, and you can jump to any moment in time.

7. Synchronization Lets people share files and stay up-to-date with the latest version.

8. Short-term undo Throw away your changes and go back to the “last known good” version in the database

9. Long-term undo Jump back to the old version, and see what change was made that day

10. Track Changes As files are updated, you can leave messages explaining why the change happened (stored in the VCS, not the file)

11. Track Ownership A VCS tags every change with the name of the person who made it

12. Sandboxing You can make temporary changes in an isolated area, test before “checking in” your changes.

13. Branching and merging You can branch a copy of your code into a separate area and modify it in isolation (tracking changes separately). Later, you can merge your work back into the common area A larger sandbox

14. VCS BASIC CONCEPT Basic Setup • Repository (repo): The database storing the files The computer storing the repo • Server : • Client : The computer connecting to the repo • Working Set/Working Copy : Your local directory of files, where you make changes • Trunk/Main : The primary location for code in the repo

15. Basic Actions • Add: Put a file into the repo for the first time, i.e. begin tracking it with Version Control. • Revision : What version a file is on (v1, v2, v3, etc.) • Head : The latest revision in the repo. • Check out: Download a file from the repo. • Check in : Upload a file to the repository (if it has changed). The file gets a new revision number, and people can “check out” the latest one.

16. Checkin Message : A short message describing what was changed. • Changelog/History : A list of changes made to a file since it was created. • Update/Sync : Synchronize your files with the latest from the repository. This lets you grab the latest revisions of all files • Revert : Throw away your local changes and reload the latest version from the repository

17. Some VCS softwares • Revision Control System(RCS) • Source Code Control System (SCCS) • Subversion (svn) • Sun WorkShopTeamWare • Concurrent Versions System (CVS) • LibreSource

18. Advanced Actions • Branch • Diff/Change/Delta • Merge (or patch) • Conflict • Resolve • Locking • Breaking the lock • Check out for edit etc.

19. CASE!!! List.txt is added to a repo. Let’s Checkinand modify over a time using a Subversion VCS.

20. Each time we check in a new version, we get a new revision (r1, r2, r3, etc.). In Subversion you’d do: svn add list.txt (modify the file) svn ci list.txt -m "Changed the list" The -m flag is the message to use for this checkin

21. Thank You !!!