Channels ▼


Subversion 1.7 Moves Into Fifth Gear

Commercially aligned Apache Subversion services company WANdisco commented on the current state of Subversion 1.7, a position the company has taken after senior Subversion developers Phillip Martin and Julian Foad made significant contributions to the planning and delivery of this major new release.

"Subversion 1.7 represents a major step forward in addressing the scalability and performance issues encountered by large Subversion deployments, especially those found on the client-side," said Hyrum Wright, Subversion's release manager and WANdisco's director of open source. "The working copy metadata rewrite (WC-NG) and HTTPv2 enhancements were key to this effort."

Key Subversion 1.7 enhancements include a protocol rewrite of HTTPv2 designed to enhance performance between Subversion clients and the server by reducing the number of round trips between the client and the server with every request. Early reviews indicate that performance improves by "orders of magnitude", although no third-party or independent (or more accurate) verification of this speed increase appears to be available.

WC-NG — a rewrite of the working copy library that enhances performance by centralizing metadata storage so that Subversion operations don't have to walk the entire directory tree to gather the information about the working copy and apply changes to it. WC-NG also provides a foundation for supporting features such as shelving and offline commits in future releases.

Merge-tracking enhancements — Subversion 1.7 provides over 40 improvements to merge tracking, on top of the improvements that were added in the 1.5.x and 1.6.x series of releases. One of the most significant enhancements has been the isolation of subtree merge info updates to only the subtrees affected by a merge, rather than updating all subtree merge info.

svnrdump — a new client tool that provides the same functionality as svnadmin dump and svnadmin load, but on remote repositories. There's no need for administrator access to the source or target repository on the remote server.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.