February 23, 2004

Subversion 1.0 released

CollabNet shipped SubversionSVN — a centralized version control system predating Git's distributed model. 1.0 on February 23, 2004 — a centralized version control system designed to replace CVS.

What it was for

Apache SubversionSubversionSVN — a centralized version control system predating Git's distributed model. (SVN) tracks file history with atomic commits, cheap branching, and real directory versioning — fixes CVS lacked. It powered thousands of corporate repos and open-source projects through the 2000s before GitA distributed version control system — commits, branches, and merges for tracking source code history. won mindshare. Typical workflow: `svn checkout`, edit, `svn commit` to a central server.

Why it's here

SVN was the mainstream upgrade path from CVS for a decade of professional development.

Why it mattered

It proved centralized VCS could be fixed without going fully distributed like GitA distributed version control system — commits, branches, and merges for tracking source code history..

What it solved

CVS lacked atomic commits and reliable branching; teams needed a drop-in successor.

Media

  • Apache Subversion
    ImageApache Subversion

    ™/®The Apache Software Foundation, Apache License 2.0, via Wikimedia Commons

Related