Is there tool agnostic terminology for source control activities?
Posted
by
C. Ross
on Programmers
See other posts from Programmers
or by C. Ross
Published on 2012-12-05T20:16:55Z
Indexed on
2012/12/07
11:19 UTC
Read the original article
Hit count: 598
version-control
|terminology
My team is entering into some discussions on source control (process and possibly tools) and we would like a tool agnostic terminology for the various activities. The environment does have multiple (old) VCS's, and multiple desired (new) VCS's. Is there a standard definition of activities, or at least some commonly accepted set?
Example activities (in CVS terminology):
- Branch
- Check out
- Update
- Merge
© Programmers or respective owner