# Apache Subversion

Centralized version control for teams retaining an established SVN repository and workflow.

ID: subversion
Language: en
Revision: 1
Translation source revision: 1
Canonical: https://kickoff.jujin.dev/en/catalog/subversion/

## Why: the goal or problem

An internal manual tells staff how to request equipment. Editors revise its pages through an existing SVN repository. Preserving that central workflow matters more than making local commits while disconnected.

## How: work toward a solution

Update a working copy, edit the request page, and inspect the difference. Commit sends it to the central repository; another editor updates to receive it. Resolve conflicting edits before retrying.

## What: the concept

Apache Subversion, or SVN, is centralized version control. Files can be edited offline, but committing history needs repository access. Git or Mercurial fits local commits; changing systems also means migrating tools and history.

[Source](https://subversion.apache.org/)

---

# Go further

Optional reading · separate from the overview

## Selection & comparison

History lives in the central repository; a working copy is not a complete history clone. Local edits and some comparisons work offline, but recording a repository revision needs access. Compare Git or Mercurial when independent local commits matter. Retaining existing SVN scripts and permissions is this example’s reason to stay.

## Applications

An editor updates the equipment manual, changes the request instructions and commits. The second editor must update their working copy to see that revision. A conflict means reviewing competing changes, not silently replacing a colleague’s page. SVN also supports branching and optional file locks; centralization does not mean every file is locked.

## Implementation & cautions

Back up and test restoration of the repository, not only working copies. Verify server access and compatibility of existing clients and hooks. Compare text merge needs with binary-file coordination; P4 is another option when asset workflows justify it. The Git-hosting choices in the other group are not drop-in SVN servers.

## Evidence

- [Apache Subversion](https://subversion.apache.org/) — Subversion is a centralized version control system. (Checked: 2026-09-27)
- [Apache Subversion: Quick Start](https://subversion.apache.org/quick-start) — Working copies, update, commit, conflicts and optional locking. (Checked: 2026-09-27)