3.
WHAT IS SOURCE CONTROL?
source control or Software Configration
Management (SCM), is the
management(sharing) of changes to
documents, Programs, and other information
stored as Computer files. It is most commonly
used in Software Development, where a team
of people may change the same files.
4. What does Source Control ever done for us?
Avoid the need to copy files from A to B.
Keep Backups so that we don't have to worry about
bad changes.
poor mans work log.
Self code Review.
5.
S
Track a
owne n
rship d
Branchi
b ng or
Tra o merging
An agreed way to xi
ck share the
cha development
n
nge resources.... g Source
s Control
Long Source control
term resources
und That give us the
B
o following.....
a
Short c
term
Sync k
undo
hroni u
satio p
6. Source control Systems:
1.Traditional Source control Systems:
Traditional source control systems 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 other's
work.
8. File Locking:
The simplest method of preventing "Concurrent access"
problems involves Locking files so that only one developer at
a time has write access to the central "repository" copies of
those files.
Once one developer "checks out" a file, others can read that
file, but no one else may change that file until that developer
"checks in" the updated version.
9. Version merging
Most version control systems allow multiple
developers to edit the same file at the same time.
The first developer to "check in" changes to the
central repository always succeeds.
Easy to merge: Text files.
Difficult to merge: Image files.
11. Results continu.....
2.Common operations are fast, because there is no need to
communicate with a central server.
3.communication is only necessary when pushing or pulling
changes to or from other peers.
4.Each working copy effectively functions as a remote
backup of the codebase and of its changehistory, providing
natural protection against data loss.
12. Terminology:
Repo Is this how you should do your repo?
No, use the TCP/IP or SVN
protocol.
Server
Client
Working set
15. List of Source Control S/W:
1.Local only
Free:
i)Rivision Control System.
ii)Source Code Control System (part of UNIX).
2.Distributed Model
Open Source:
i)Bazaar.
ii)Codeville, iii)mercurial(i to iii are written in python).
iv)SVK (wrutten in Perl).
17. CONTINU..........
Proprietary:
i)Telelogic synergy(Proprietary of IBM).
ii)Vault[version control tool by SourceGear (First installation
can be used for free)].
iii)Visual SourceSafe
iv)Visual Studio Team System
Iii &iv are Version ctrl tool by
Microsoft
