Apache Subversion is fortunate to have a community that values documentation. This page contains pointers to varies sources of documentation aimed at Subversion users and developers both of Subversion and of third-party tools with which Subversion integrates. Much of this documentation is itself freely licensed, so if you spot errors in them, please feel free to submit corrections to the relevant owners of the documentation.
If you want to know how to use Subversion, you can find a number of published user manuals available for purchase online. One of these texts — Version Control With Subversion (affectionately known as "the Subversion book") — carries a free license, was developed openly by the Subversion community itself, and is also available in full online for free at http://svnbook.red-bean.com.
Release notes for each minor release series, describing its major features, differences, and upgrade caveats with respect to prior release lines, are available:
The Subversion community operates at peak efficiency when everyone honors the various policies which were established by the community as the result of years of experience. The following documents provide invaluable insight into How Stuff Gets Done Around Here. We hope you find them useful not only as you contribute to Subversion, but also as you then seek to develop and establish best practices in your own software projects.
Subversion is a collection of modular libraries written in the C programming language, each of which has a clearly defined collection of functions and types that together make up Subversion's application programming interface (API). This API is stable within major release streams of the software itself, so if you write software that uses Subversion 1.1.0's interfaces, you should expect that software to continue to work when the Subversion libraries are upgraded to 1.6.0 without your having to change or recompile your software at all.
The follow documentation is offered for pre-release testing. The usual caveats apply, including the fact that there are known issues, and no upgrade path is promised for APIs and on-disk files (working copies and repositories) between the pre-releases and the final release.
NOTE: Unreleased documentation is provided by volunteers who offer such as a service to (primarily) Subversion's own developers. Such documentation has not been validated by Subversion's official release procedure, does not necessarily describe stable APIs, and is itself not guaranteed to be either accurate or complete. Please keep these facts in mind while using these documents.