Svn

Subversion (SVN) is a centralized version control system that manages changes to files and directories over time. It stores the full project history in a central repository, and each commit creates a new revision identified by a monotonically increasing number.

SVN uses a central repository with working copies checked out by developers. Changes are committed back to the repository. Projects commonly organize content under trunk, branches, and tags. Branching and tagging are implemented as directory copies. Access to the repository can be via svnserve or over HTTP(S) with Apache.

Typical workflows start with checkout to obtain a working copy, followed by edits and commits to record changes. Users can update to synchronize with others, view history with log, and compare changes with diff. Merge operations resolve conflicts, and commits are atomic.

Origins and status: SVN originated in the early 2000s as a replacement for CVS and has been maintained by the Apache Software Foundation. It remains in use in many organizations that prefer centralized control and explicit access management. The rise of distributed systems has reduced its prominence, but it remains stable and mature.

Strengths and limitations: SVN provides centralized control, atomic commits, and good performance for large repositories and binary assets when configured. Its network dependency and sometimes more complex merge workflows are noted drawbacks, compared with distributed version control systems such as Git.