Version control

Version control records changes to files over time so revisions can be compared or restored and concurrent work can be coordinated.

Repository: A data structure or storage location that holds files and their revision history. Version control stores project files and their history in repositories.
File system: A system for organizing, naming, storing, and retrieving files. Version control tracks changes to files organized in a file system.
Git: A distributed version-control system designed to track changes in files and coordinate collaborative work. Git is a widely used implementation of version control.
Centralized version control: A version-control architecture in which a central server stores the authoritative project history. It contrasts with systems that give each collaborator a complete local history.
Collaborative software development: The creation of software through coordinated work by multiple contributors. Version histories let contributors work in parallel and integrate their changes.
Commit: A recorded set of changes to files, identified in a revision history. Commits mark saved states that later revisions can compare or restore.
Revision history: An ordered record of successive states or changes to an artifact. A revision history is the record version control creates and maintains.
Subversion: A centralized version-control system that maintains a shared repository and revision history. Subversion illustrates the centralized approach to managing project revisions.
Distributed version control: A version-control architecture in which each clone contains the project’s history. It contrasts with centralized systems that depend on a shared authoritative repository.
Code review: The examination of source-code changes to identify defects and improve quality. Recorded changes give reviewers a bounded, inspectable unit of work.

Linked from 25 pages