Upgrading to Subversion 1.7

Upgrading to Subversion 1.7

Xcode 5 now includes Subversion 1.7.

When you check out a new working copy in Xcode 5, Subversion 1.7 is automatically used. When you first launch an existing project in Xcode 5, you are presented with an option to upgrade from
Subversion 1.6 to Subversion 1.7. Unless you are still using a previous version of Xcode, it is strongly encouraged that you upgrade.



Important: After
upgrading to Subversion 1.7, you cannot go back to Subversion 1.6.

Subversion 1.7 provides many benefits:

Improved performance. Increased speed for many common source control operations, most notably a significant increase in checkout speed.

Blame for modified files. With Subversion 1.7, you can provide blame annotations for files modified locally. Previously this was only possible when using Git.

Blame for line. View just the blame for a specific line in a files as opposed to seeing all of the blame for an existing file.

Command-line integration. Only Subversion 1.7 commands are accessible through the command line.

Improved file organization. Subversion 1.7 provides a cleaner file structure by centralizing the Subversion metadata. Instead of having

.svn

files
inside each directory of a checkout, there is now just a single

.svn

file in the root of a checked out directory.

If you choose not to upgrade to Subversion 1.7 initially, you can upgrade your working copy at any time by choosing Source Control > Working Copy > Update.