Tag Archive for 'subversion 1.7'

Subversion Live 2012:Keynote

After a first day that covered hook scripts, Subversion server tuning and best practices, and still found time for a Birds of a Feather Open Session, there was even more good stuff to come at the second day of Subversion Live London.

Day two featured an afternoon of breakout sessions that took in the new Apache Bloodhound project, branching and merging, move tracking, continuous delivery, and more.

The day kicked off bright and early, with a keynote delivered by Greg Stein, the Vice President of Apache Subversion at the ASF.

Despite the early hour, Greg delivered his ‘Why Subversion Still Matters’ keynote to a full room. Over the course of an hour, he covered the entire history of the world’s most popular version control system, from the initial “Inversion” filesystem design, to the first Milestone releases, and finally onto Subversion 1.7 as we know it today, complete with enterprise features that are seeing SVN gain increasing adoption within enterprise environments.

Greg also shared the story of how the team assumed Subversion 0.14.0 would mark a turning point in SVN’s development, with future development being concerned only with “bugfix and minor features from now on.” This was backed up by a slide aptly titled “What Were We Thinking?!?”

Greg shared his thoughts on maintaining and managing an open source community, stressing the importance of making developers feel a part of this community by granting them committer privileges. This encourages Subversion’s long-term health – inevitably, some developers will leave the project, but there are always new committers joining.

Of course, any ‘Why Subversion Still Matters’ talk ultimately boils down to the hotly-contested question of whether SVN is still relevant, and whether the future of version control really lies with distributed systems such as Git. Greg pointed out that when you use services such as GitHub, you effectively make your distributed version control centralized again, but ultimately took a refreshingly pragmatic approach, advising that version control systems are just a tool and you should simply choose the right one for your needs.

After covering the ins-and-outs of Subversion’s past, there was just enough time to look to the future. Greg assured attendees that the committers are “always improving merging and merge conflict detection,” and that, although future releases will feature more disconnection, they will still maintain a canonical server.

Despite taking in the entire history of Subversion and looking ahead to future releases, many attendees took advantage of the opportunity to put further questions to Greg Stein after the session had ended.

Poll: What’s your Favourite Feature of Subversion 1.7x?

After finding out more about the way you’re using Apache Subversion in our recent community polls (‘Which OS does your Subversion Server Run On?’ and ‘Which Subversion Client Do You Use?’) we need your input again – this time, on the Subversion 1.7 series.

Apache Subversion 1.7 was a major step forward for the world’s most popular open source version control system, and the subsequent releases have brought even more enhancements and fixes to the series. But what’s your favourite new feature of the 1.7 releases? Let us know, by answering our quick, one-question poll!

Take the poll now.

We’ll publish the results in a few weeks, so be sure to keep checking back to see how your Subversion usage compares to the rest of the community.

Haven’t made the switch to Subversion 1.7 yet? The latest binaries in the 1.7 series can be downloaded from the WANdisco website: http://www.wandisco.com/subversion/download

Commitment to the Cause

“There’s a difference between interest and commitment. When you’re interested in doing something, you do it only when circumstance permit. When you’re committed to something, you accept no excuses, only results.”

I think it’s a wonderful quote, primarily because it’s true.  There really are only two options regarding commitment, you’re either in or you’re out. There’s no such thing in life as inbetween.  WANdisco is very much “in” when it comes to Apache Subversion.

Today we made a couple of very important announcements.

  1. We upped our sponsor level of the ASF from Bronze to Silver.
  2. We increased the number of full-time subversion committers by hiring two of the most experienced Subversion engineers in Branko Čibej and Stefan Fuhrmann.

The ASF is a non-profit, volunteer-run foundation and this will help aid organizational, legal and financial support for a broad range of Apache licensed projects including Subversion. We continue to be extremely grateful to the ASF.  This is a ‘safe home’ for Subversion.  Apache have led the way in community open source development since 1999 and they are no stranger to mature, pervasive open source technology like Subversion.

Branko and Stefan are two wonderful software engineers with lot’s of experience in the SVN community.  Branko has been involved in the project since 2000 and he has always worked on some of the most difficult and complex problems.  Karl Fogel told me a long time ago that he could really help deliver the branching and merging improvements we hope to make.

Stefan has worked on the Subversion client TortoiseSVN since 2003 and now spans both client and server.

I think this is great news for the community as a whole.

This announcement coincides with the second year of our Subversion Live Conferences.

The first year we ran the events they were a huge success.  It presented a unique opportunity for Subversion users from a wide spectrum of organizations to interact with each other and the core Subversion developers.  Registration is now open here:  http://www.wandisco.com/svn-live-2012

avatar

About David Richards

David is CEO, President and co-founder of WANdisco and has quickly established WANdisco as one of the world’s most promising technology companies. Since co-founding the company in Silicon Valley in 2005, David has led WANdisco on a course for rapid international expansion, opening offices in the UK, Japan and China. David spearheaded the acquisition of Altostor, which accelerated the development of WANdisco’s first products for the Big Data market. The majority of WANdisco’s core technology is now produced out of the company’s flourishing software development base in David’s hometown of Sheffield, England and in Belfast, Northern Ireland. David has become recognised as a champion of British technology and entrepreneurship. In 2012, he led WANdisco to a hugely successful listing on London Stock Exchange (WAND:LSE), raising over £24m to drive business growth. With over 15 years' executive experience in the software industry, David sits on a number of advisory and executive boards of Silicon Valley start-up ventures. A passionate advocate of entrepreneurship, he has established many successful start-up companies in Enterprise Software and is recognised as an industry leader in Enterprise Application Integration and its standards. David is a frequent commentator on a range of business and technology issues, appearing regularly on Bloomberg and CNBC. Profiles of David have appeared in a range of leading publications including the Financial Times, The Daily Telegraph and the Daily Mail. Specialties:IPO's, Startups, Entrepreneurship, CEO, Visionary, Investor, ceo, board member, advisor, venture capital, offshore development, financing, M&A

Apache Subversion: Still on Top in 2012

One of the common criticisms levelled at Apache Subversion is that, as a non-distributed version control system, it’s getting a bit long in the tooth, and the future of version control lies with distributed systems like GIT.

At WANdisco, we’re convinced this isn’t the case, and that Subversion is actually going from strength to strength. Only last year, Subversion 1.7 was released, a major step forward for the platform that included a completely rewritten working copy metadata system, support for a new HTTP protocol variant, ‘HTTPv2,’ and the svnrdump tool. When we polled the Subversion community a few months after this major update, we found that a whopping 68% of those surveyed had either upgraded as soon as 1.7 was released, or were planning to upgrade in the near future.

This proves that Apache Subversion still has an active user base, who are eager to upgrade to new releases of SVN. This is crucial to the ongoing success of Subversion as increasingly, the success of software hinges on “technology populism,” where individual workers, not organizations, create business trends. Subversion is easy to install, with a relatively easy learning curve and less administrative overhead than many competing version control solutions, and therefore we’re confident of its continued success in this increasingly tech populism-driven marketplace.

As you may already know, WANdisco is one of the major corporate sponsors of the Apache Subversion project. We provide a full suite of Enterprise products based on SVN, including Subversion Access Control, Subversion MultiSite and Subversion Clustering. We also offer professional support for Subversion and TortoiseSVN – but it doesn’t end there! We’re so confident that Apache Subversion is the leading version control solution, that we based our own open ALM platform on Subversion, uberSVN.

Since its launch last year, not only has this unique, SVN-based product been awarded the Made in Sheffield mark and Business IT Innovation of the Year medal, but it’s received a positive response from the community, as well as some fantastic reviews by the IT media. But what about the figures? Since its launch, we’ve had on average over 2000 downloads per month. For a brand new product, this is nothing short of amazing, and is further proof that the Subversion community is as vibrant and forwardings-looking as ever.

Subversion is also gaining momentum in the Enterprise space. The customer list for our Enterprise Subversion solutions reads like a who’s-who of the industry: HP, Intel, Sony, Nokia, Barclay’s Capital, Disney, Skype, Honda, and more. TortoiseSVN has also become the defacto standard Subversion client for Windows – most, if not all, of our Fortune 1000 clients use it.

With the 1.7 maintenance releases coming thick and fast, we’re confident that the future looks bright for uberSVN, WANdisco’s Enterprise Subversion products and, most importantly, the Apache Subversion project itself.

If you’re an avid Subversion user, then why not get involved in the project? The Apache Subversion site has all the information you need to contribute to the project.

Apache Subversion 1.7.5 Released

The Apache Subversion community has released another update to the popular version control system. The just-released Subversion 1.7.5 features a string of enhancements, including a performance improvement for scanning the working copy root, and a memory and file-handle management improvement. As usual, the release also includes some bug fixes:

  • a fix for regression from version 1.6 in update with –depth option
  • a fix for a potential use of already freed memory during diff operation
  • fix ‘svn update –depth=empty’ against 1.4 servers
  • a fix for undefined behaviour during multi-segment reverse merges

As ever, the latest binaries are available for free download from the WANdisco website, and users of uberSVN, the free, open ALM platform for Apache Subversion, can easily upgrade to 1.7.5 from inside their installation. uberSVN is free to download and free to use, and not only did it turn one year old last month, but it came out of beta testing, to boot! uberSVN had a hugely successful first year: it was awarded the Made in Sheffield mark and Business IT Innovation of the Year medal, and has received an overwhelmingly positive response from the community.

The full list of what’s new and noteworthy in Apache Subversion 1.7.5, is available in the Changes file.

Poll Results: Are You using Subversion 1.7 Yet?

At WANdisco, we’re convinced that Apache Subversion 1.7 is a great release. Not only did it completely overhaul the working copy metadata system, but it added support for HTTPv2 and a new remote dumpfile tool. But, we wanted to know how many of you had already made the switch to Apache Subversion 1.7 – so earlier this month, we held a poll at SVNForum.org, to find out who has switched, who is planning to, and who is content to stick with their earlier release of Subversion.

Click on the thumbnail below to see the full results of our poll:

Thank you to everyone who took part in our poll! We had a great response from the Subversion community.

Do you have a burning, SVN-related question you would like to put to the Subversion community? We’ll be running regular polls throughout the year, so feel free to post your poll ideas in the Comments section or, alternatively, contact us directly.

March of the uber

Admin Console - LDAP

So, we thought it would be good to give you a ‘broad stroke’ update on what’s going on in the world of uberSVN. Firstly, you’ll probably have noticed that another update recently appeared; a modest interim fix that sorts out some niggles encountered by Subversion 1.7’s early adopters. If you didn’t catch the update, here’s what changed:

uberSVN – Release 11.11

What’s New

[Portal] It’s no longer possible to browse to cached screens without re-authorization. (ESVNB-2157)

[Portal] We’ve cleaned up the layout of the uberSVN login screen. (ESVNB-2265)

[uberAPPS] We’ve changed our back-end server to use the C3P0 connection pooling library to improve the handling of long running connections to the database. (ESVNB-2267)

What’s Fixed

[svnSWITCH] We’ve fixed an issue where running with Subversion 1.7 stopped the repository browser from working. Also fixed is the problem with repository browsing that occurred if you switched to Subversion 1.7 when using SSL. (ESVNB-2468) (ESVNB-2473)

[svnSWITCH] Windows XP users are now able use the SVNswitch tool. (ESVNB-2471)

[svnSWITCH] Activating Subversion 1.7 no longer stops commit activity from being reported on the dashboard or repository activity stream. (ESVNB-2472)

The bigger picture

This is the 7th update in the 7 months since our first release – from that you can probably work out the release cycle that we’re aiming for, and so far hitting. This release tempo should also tell you that there’s been no slow-down here at WANdisco’s Sheffield-based software forge – indeed, if cities had middle names, Sheffield’s might be ‘Industrious’, and it’s hard for a developer of software tools to not be inspired by a city that unexpectedly became the world’s supplier of industrial tools.

If that allusion to Sheffield’s heritage seems like big talk from a small “upstart”, maybe it’s because we know we’re on to something and we’ve got the potential to change the game, if we can keep on course, and keep on delivering regular improvements. To this end we’re very happy with the results we’ve got from an Agile approach. Keeping your releases bite-sized but regular forces you to keep the focus on stuff that works rather than trying to build Rome in a day. Of course, in an office with a giant slide, who needs to ride the waterfall?

Now we’d concede that this might give the impression that the big changes are never coming, in fact you can be sure that they are. Our Suggestion Website has given us an invaluable insight into what many of you like about uberSVN, but more importantly it tells us what holes we need to fill. Full LDAP integration, Defect tracker, anyone? We are hard at work on plugging both into uberSVN, as well as a few other things-that-you-want. Of course, there are lots of features and capabilities that fall outside the scope of what we can build ourselves, we’ll still be able to deliver these through uberAPPS, which will soon benefit from another round of enhancements, and some cool new APPS for you to buy

It’s your turn

For us, uberSVN’s social coding element is important because software development, at its best, should be a conversation – sometimes, an argument. So we’ll ask again, keep asking us for stuff, most definitely keep telling us what we’re doing wrong. Most of all, keep talking.

Not given uberSVN a try? It’s here, it’s FREE, and so easy to install your kids could do it – in fact, ours did. http://www.ubersvn.com/

Top Ten Reasons to Switch to Subversion

It’s no secret that WANdisco are big fans of Subversion! But we know that Subversion is far from the only revision control system on the market, so what makes Subversion so special? Here are our Top Ten reasons to give Subversion a go!

1) It’s Established – Accepted into the Apache Incubator in 2009 and graduating a year later, Subversion has been an Apache Top Level Project for well over a year, and is today maintained by a global community of contributors. Furthermore, in 2007, independent technology and market research company Forrester Research identified Subversion as the sole leader in the Standalone Software Configuration Management category, and as a strong performer in the Software Configuration and Change Management category.

2) Increasing corporate adoption of open source – Open source is enjoying increasing acceptance within the enterprise. There are plenty of reasons to adopt open source solutions, but cost is the most obvious one. With closed source solutions, there’s the initial outlay, but there can also be some hidden extras: the expense of ongoing upgrades, extra licenses if the team expands, training costs, etc. Open source solutions reap the benefits of potentially thousands of developers, all contributing their expertise to the same project. This typically means shorter release cycles than some closed source projects, and this sort of collaborative development also encourages transparent, archived communication through mailing lists and forums. This communication can be an invaluable (and free!) source of information for the Subversion user. As an open source project with all of this to offer, it’s easy to see why Subversion is gaining popularity within the enterprise! Many Fortune 1000 companies use Subversion: AT&T, Intel, Honda, Nokia, Juniper Networks and Motorola all rely on WANdisco’s Subversion solutions.

3) Vibrant ecosystem – Apache Subversion has a vibrant ecosystem of users who can be contacted for advice via mailing lists and forums. This ecosystem also includes many free client tools (including TortoiseSVN) GUIs and plugins, developed by the community. In fact, there are integrations for most – if not all – of the major IDEs: Eclipse, Microsoft Visual Studio, etc.

4) Commits as true atomic operations – commit operations to any number of files and directories are automatically published as a single atomic transaction. Every commit operation will either succeed completely, or fail completely; this guards against a situation where some of the committed files make it into the repository, and others do not. Where atomic transactions aren’t supported, interrupted commit operations can lead to repository inconsistencies or corruption.

5) Established professional support options – open source solutions can be a real asset to a project, but there are some common concerns many organizations have, regarding open source. Subversion has a great community of users who are always willing to help out, but mailing lists and forums aren’t always the ideal place to reach out to when disaster strikes your organization! Thankfully, established open source projects often have professional support options that can alleviate these worries, and Subversion is no exception! At WANdisco, we offer professional support services for Subversion, that include 24-by-7 worldwide coverage, guaranteed response times, indemnification coverage, and even help migrating to the latest and greatest version of Subversion, Subversion 1.7x.

6) Branching – Subversion supports the concept of ‘branches,’ lines of development that exist independently of another line. Branches allow developers to work on code, independently of the work going on in the trunk. None of the changes made within a branch are seen by people working in the trunk, or in any other branches, until a merge is performed. Subversion has a range of functionality for users working with branches, including commands for maintaining parallel branches, and the ability to make parts of the working copy reflect different branches. Subversion also remembers which branches are related to one another.

7) Merging – in Subversion, when multiple developers are working on the same project simultaneously, files do not need to be locked to ensure that only one developer at a time has access to the central repository of those files. Instead, Subversion encourages ‘merging,’ which is the act of replicating changes from one branch to another. Merging increases productivity, by eliminating time wasted by developers queuing up to access the same source file.

8 ) Easy to administer – when compared to competing revision control systems, administrative overhead for Subversion is fairly light.

9) Subversion 1.7 – We can’t think of a better reason to start using Subversion than a brand-new, major release! Subversion 1.7 introduces some long-awaited functionality, including:

  • WC-NG – a complete rewrite of the working copy metadata system.
  • Pristines – a new way of storing text-bases in 1.7.
  • Merge-tracking enhancements – over 40 improvements to merge tracking.
  • HTTPv2 – a new HTTP protocol variant designed to enhance performance between Subversion clients and the server.
  • A new in-memory caching system for FSFS repository backends.
  • Network compression – a protocol for avoiding CPU bottlenecks on the compression side.
  • svnrdump – a new client tool that provides the same functionality as svnadmin dump and svnadmin load, but on remote repositories.

10) Open and extensible architecture – Subversion can be used as the foundation for your software development lifecycle. This is exactly what we have tried to do with uberSVN, WANdisco’s open ALM platform for Subversion! With uberSVN, WANdisco set out to transform Subversion into an open, extensible platform for ALM that gives users the widest choice of toolsets, with no vendor lock-in. uberSVN is free to download, easy-to-install and easy-to-use!

Have we convinced you to give Subversion a go? The latest Subversion binaries can be downloaded from the WANdisco website. And if you want to find out more about uberSVN, our ‘Top 10 Reasons to Try uberSVN’ blog post is a great place to start!

Top 10 Reasons to Try uberSVN

Launched in April, WANdisco’s uberSVN platform is a major new product designed to transform the world’s most popular source code management system into an open, extensible platform for ALM, empowering Subversion users by giving them the widest choice of toolsets with no vendor lock-in. With uberSVN, WANdisco set out to give developers exactly what they want: an easy-to-install, easy-to-use open ALM platform for Subversion, that they can extend however and whenever they choose, crafting their own complete, best-of-breed ALM solution. In this post, we’ll run through the Top 10 reasons to give uberSVN a go today:

1) Easy to administer:

The uberSVN dashboard is divided into four main areas, giving you an insight into the overall status of your Subversion implementation’s servers, repositories, and all the users’ latest activities.

  • Tabs – These allow you to drill down into the individual repositories, users, and teams.
  • Activity Stream – This is where all messages and changes to the repositories are displayed. Actions displayed include: when a user commits to a repository, or makes administrative changes to a user or a team. Social actions, such as team members’ comments on postings and activities, are also displayed.
  • List of repositories – This is where you can view all the repositories that have been added to uberSVN.
  • Quick Links – This is where you can define quick links to both specific areas within the repositories, and to outside applications that are part of your development lifecycle.

2) Easy to collaborate:

uberSVN works on the concept of ‘teams;’ allowing groups of people to be assigned certain access privileges. Working in teams in uberSVN has the following benefits:

  • Easy to add new members. Once you’ve defined what a team can do inside specific repositories, you never really have to define user access again. When adding a new user to an existing team, they will automatically be assigned the relevant access privileges.
  • Easy to change access controls. A large organisation might have dozens of teams, each with different access controls to different repositories. Traditionally, changing access control for one team, would require each team member’s privileges to be altered individually – an administrative nightmare! With uberSVN, not only are access privileges easier to setup, they are easier to control, as you can assign and remove entire teams from a repository.

3) Easy to Manage Multiple Repositories:

In today’s organizations, it’s common for development teams to be working on multiple projects, across multiple repositories, and uberSVN’s filtering system helps you keep on top of this. With uberSVN, you are always looking at a defined set of information; for example, information about all the users, all the teams, etc, that relate to a repository. If you then select a particular repository, you can view all the commit messages, comments, users, etc, that relate to that repository. By helping you manage and organize information across multiple repositories, uberSVN keeps you from getting overwhelmed. Of course, all of this information (save for the comments made within uberSVN’s social coding environment) could be gathered from the log information in a repository but, crucially when dealing with multiple repositories, uberSVN lets you drill down to the information that is most relevant to you.

4) Freedom to Choose:

Previously, Subversion users have had two options when extending Subversion into the ALM sphere. The first, is to go with a closed source ALM solution that leverages Subversion for version control, but imposes a vendor lock-in. The users have no freedom to tweak the implementation to suit their own needs, and when their requirements evolve beyond the vendor’s specific solution, it has to be replaced entirely. A hand-crafted solution assembled from a variety of components, does give the users the freedom to tailor a solution to suit their particular needs, but this freedom comes at a cost:

  • a lack of integration. There is no guarantee that the product will work throughout the development lifecycle, or will interconnect with all the other elements of the software system.
  • a lack of documentation.
  • no professional support option.
  • they rely on brittle, home-grown scripts that require no specialist knowledge to maintain.

uberSVN aims to give the developer all the freedom of a homegrown solution, but with the support and integration you’d expect from a closed source ALM solution. With uberSVN, developers can:

  • replace specific components as requirements evolve, or as better tools become available.
  • choose from both open and closed components.
  • stick with their own open or closed source defect trackers, build servers, etc, even if an alternative is available in the Apps store.

5) Social Coding Capabilities:

uberSVN combines Twitter and Facebook-like capabilities, to provide a social coding environment out-of-the-box and bring social networking functionality into your development environment. In uberSVN, each development team has its own home page with profiles of the team members and information such as the projects they’re working on and the repositories they’re using. This functionality is particularly useful in modern IT organisations, where development teams tend to be working on multiple projects, on multiple repositories. Not only does this enable team members to keep track of one another’s real-time progress across all repositories, but managers can leverage uberSVN’s social coding capabilities to keep track of the status of projects. There is also a chat facility for instant communication.

6) Integrated App Store:

We know that there’s no shortage of tools out there, but we also know that you don’t always have the time to define the applications that will add the most value to your Subversion experience. Therefore, uberSVN comes integrated with uberApps; a one-stop shop for software development lifecycle applications for the enterprise. We have tested the integration and installation of every tool in the app store for you, so every application comes pre-certified to integrate with the uberSVN platform, without the hassle of testing it yourself.

With one-click to purchase and one more click to install, simply select the tool you want from uberApps, select the install button, and you’ll be guided through installation. This is a streamlined version of the traditional installation process; for example, if you wanted to install Jenkins, usually you would visit the Jenkins CI site, install it on your machine and run a Java jar on the war file. Now, Jenkins is available straight from the uberApps store. And, if you need some extra help, WANdisco provide professional support services, and are your single port of call for assistance with either uberSVN, or any of the applications downloaded from uberApps.

7) Easy to Install:

With a GUI-based installation and no prior Subversion experience assumed, uberSVN is designed to be easy to install. On the installation screen, simply specify your installation settings, including your:

  • installation directory.
  • the directory located in your first Subversion repository (more can be added at a later date through the “create repository” option in the admin console.)
  • uberSVN License Key

And that’s it! Although uberSVN is designed to be easy to install, Subversion experts can easily change the model configuration to suit their own particular needs.

8 ) Support:

Homegrown solutions may give you the freedom to choose the open and closed source components that work the best for you, but they lack the professional support you’d get with a closed source ALM solution. With uberSVN, we combine the freedom of a homegrown solution with a professional support option. uberSVN support includes:

  • 24-by-7 online, phone and email support.
  • guaranteed response times.
  • automated delivery of fixes and upgrades.
  • global coverage from the US and Europe.

9) Toggle Between Latest Releases

Subversion 1.7 introduces some great new features, but we know that upgrading core technologies can be a scary business! To make the leap to Subversion 1.7 easier, uberSVN 11.10 includes an innovative new svnSWITCH tool that gives the administrator the freedom to upgrade to 1.7 with just a click and a server restart – even better, the switch is just as easily reversible. This gives users the option of upgrading to 1.7 to take advantage of the new features, but with the safety-net of downgrading to 1.6 if required.

10) …..and it’s free!

A free download of uberSVN is available now, for the Windows, Linux and OSX platforms.

Subversion 1.7: Five Reasons to Migrate

The Apache Software Foundation have announced the general availability of 1.7; but how exactly will the new features in 1.7 affect the user? And why should you upgrade to version 1.7? Here are five good reasons, to make the leap to Subversion 1.7 today:

1) Completely Rewritten Working Copy Metadata System

In Subversion 1.7, the working copy metadata system has been completely overhauled. For the user, this means:

  • An immediate performance boost. All the metadata for the whole working copy is now stored in a single datastore in the root of the working copy, so Subversion operations no longer have to walk the entire directory tree to gather all the necessary information about a working copy.
  • Many small fixes (e.g WC-NG uses a generated index key to avoid case-sensitive file name issues) that together add up to a much more robust metadata storage system.
  • Get ready for the future! The original WC library had grown so complex, that introducing new features was becoming a real effort. WC-NG paves the way for new features, beyond 1.7.

2) Improved HTTP Protocol

For 1.7, the Subversion team decided to drop DeltaV in favor of a new HTTP protocol variant, ‘HTTPv2.’ This has a number of benefits for the Subversion user:

  • Removes the overheads associated with DeltaV (e.g additional port find requests in the Apache log file of a Subversion server.)
  • Fewer client-server round trips per request means enhanced performance between Subversion clients and the server.
  • Reduced server load (due to fewer requests to log and fewer accesses to the repositories.)

3) Get Control Over Your Cache

Version 1.6 introduced an in-memory caching system, but many users experienced problems with an increasing amount of memory being allocated to the cache. Subversion 1.7 gives you greater control over your cache:

  • Functionality for controlling how much memory is used by the cache, to prevent the amount of memory allocated to the caching growing out of control.
  • New caching structure and new code that has a better behaviour, regarding memory usage.

4) Configurable Data Compression Rate

Users with a high enough bandwidth can end up spending more time on the compression and decompression of data, than they gain by sending compressed data. 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.

5) New ‘svnrdump’ Remote Dumpfile Tool

Subversion 1.7 gives users the ability to replicate the functionality of svnadmin dump and svnadmin load on remote repositories. No administrator access to the source or target repository required!

Certified open source Apache Subversion 1.7 binaries can be downloaded from our website or, alternatively both Subversion 1.6 and 1.7 are available in our free, open ALM platform, uberSVN.