view content/SCM/subversion-1.7.md @ 98:1d9382b0329b

Specify the syntax on markdown blocks to avoid broken output that has class=err
author Dirk Olmes <dirk@xanthippe.ping.de>
date Thu, 19 Dec 2019 10:04:33 +0100
parents 4cd9b65e10e4
children
line wrap: on
line source

Title: Subversion 1.7
Date: 2013-01-07
Tags: Subversion
Lang: en

Recently I received a portage update to Subversion 1.7. Since this version uses a new working copy layout I was a bit sceptic about how much work upgrading to 1.7 would really be.

So far the update went really smooth. I upgraded the svn client and had to migrate (svn upgrade) the working copy. The working copy is significantly smaller after the migration:

<table border="1" cellpadding="5">
    <tr>
        <th>&nbsp;</th>
        <th>Subversion 1.6</th>
        <th>Subversion 1.7</th>
        <th>Size diff</th>
    </tr>
    <tr>
        <td>customer project 1</td>
        <td>957M</td>
        <td>676M</td>
        <td>70.64%</td>
    </tr>
    <tr>
        <td>customer project 2</td>
        <td>14M</td>
        <td>7.5M</td>
        <td>53.57%</td>
    </tr>
    <tr>
        <td>Mule community 3.x</td>
        <td>342M</td>
        <td>200M</td>
        <td>58.48%</td>
    </tr>
</table>

SVN operations like running an update or reverting a lot of changes seem to be a bit faster. I can't say if subversion in Eclipse behaves faster or not - haven't my mind made up just yet.

I'll leave the server part and all the related tools (Jenkins, Sventon etc.) for another post later.