Subversion 1.7: Three Reasons to Migrate Now

Currently described as the “best Subversion release of its time", Subversion 1.7 is now available for immediate download from the Apache website http://subversion.apache.org/download/.

Why make the move to 1.7 now?

1) Greater Cache Control

• Subversion 1.7 gives you greater control over your cache eliminating previous issues with the in-memory caching system experienced by users is version 1.6.
• Control the amount of memory allocated to the cache to help prevent an overload.
• A new and improved caching structure and with code that cooperates more favourably with memory usage.

2) New and Improved Working Copy Metadata System

• Significant Performance Enhancements: Centralised metadata storage, Subversion operations can now obtain required information about a working copy without having to walk the entire directory.
• A number of fixes: Together to produce and all round more robust metadata storage system.
• Get ready for the future: The complexities of the original WC library have been banished. WC-NG paves the way for new features, beyond 1.7.

3) Configurable Data Compression Rate

Subversion 1.7 allows the user to configure the data compression rate; by sending uncompressed data on a high bandwidth, the server has a lower load and can respond faster, resulting in noticeable performance enhancements.

Plus many more exciting new additions: http://subversion.apache.org/docs/release-notes/1.7.html.

Upgrade Now!

With great new features and fantastic enhancements, upgrade to Subversion 1.7 now with Clearvision.

Clearvision's extensive understanding of development best practices and solid background in Subversion enables us to successfully upgrade your subversion critical system with minimal downtime and impact to your development team.

Migrating from IBM Rational ClearCase?

Moving to the open source version control tool Subversion does not necessarily mean losing your version history, unlike all existing migration tools Clearvision’s Migrate2SVN works effectively while retaining the historic relationship between branches, labels and versions.