PAUSE
BOTCLEAN
ENCORE5
CLEAN
ENCORE
BOX
ILLUSTRATION
GO
Source Code Control Diagram
In the process of software development, a company
may have 1 major release once every 2 years, and
some minor updates (levels) in between that period, e.g.:
@-------@-------@--------@--------@--------@ <--- release.level
1.1 1.2 1.3 1.4 2.1 2.2
The branch itself is associated with another level of update,
referred to here as sequence. Naturally the first sequence
on a branch is 1.
>branch, sequence
/
branch 1 @ <----------/
/1.3.1.1
/
/
@-------@-------@--------@--------@--------@ <--- release.level
1.1 1.2 1.3 1.4 2.1 2.2
Each extra update in the direction of the branch is a new sequence,
while change in direction of an update is a new branch, e.g.:
1.3.1.2 branch 1
@ <-----------\
/ 1.3.3.1 \
/ >branch, sequence
/ branch 2 /
branch 1 @-------@ <----------/
/1.3.1.1 1.3.2.1 1.3.3.1
/
/
@-------@-------@--------@--------@--------@ <--- release.level
1.1 1.2 1.3 1.4 2.1 2.2
Extra sequences and branches can be added in the process of
software development:
1.3.1.2 branch 1
@-------@-------@ <--
/ 1.3.3.1 1.3.3.2 \
/ >branch, sequence
/ branch 2 /
branch 1 @-------@ <----------/
/1.3.1.1 1.3.2.1 1.3.3.1
/
/
@-------@-------@--------@--------@--------@ <--- release.level
1.1 1.2 1.3 1.4 2.1 2.2