Is there tool agnostic terminology for source control activities?
- by C. Ross
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