Version control
A system that records changes to tracked files and makes earlier states comparable.
Preserve changes as history
Version control records file changes so saved states can later be compared and, when needed, restored. This can cover source code, configuration and documentation. Its scope depends on which files are actually tracked and which history is retained.
In a fictional example, a changed date display in a report needs investigation. Recorded history helps find the previous state and relevant change; a clear change description adds the reason. Restoring tracked files does not restore production data changed in the meantime. Back up the repository and other operational data with appropriate methods for each. Version control and semantic version numbers serve different purposes.
Sources
Related terms
- GitA distributed version control system with local repositories and recorded change history.
- BranchA named development line that Git tracks through a movable reference to a commit.
- CommitA recorded project state with metadata and, where applicable, links to earlier states in Git.
- Semantic versioningAn agreed version scheme expressing intended compatibility of changes to a defined public API.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps