[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: release date of Subversion 1.7

From: Todd Gleason <Todd.Gleason_at_elekta.com>
Date: Sun, 10 Apr 2011 19:11:07 -0700

> > To be frank, we have been unable to find a compelling reason to
> upgrade our server from 1.5, though on the client end we use 1.6
> versions. The unfortunate thing is that the various improvements made
> since early 1.5 have almost never said (in the release notes) whether
> they were on the client or on the server, and we cannot justify the
> cost/risk of an upgrade without knowing more specifics.
> The release notes at
> http://subversion.apache.org/docs/release-notes/1.6.html indicate
> client vs. server on quite a few of the changes, and at least a few of
> the ones that aren't marked are pretty clear from the description
> which they affect.

I should have been more specific. The release notes tells us a bit, but the changes file at


has the real details I am usually interested in. Here are a few of interest:

   * fix potential crash when requesting mergeinfo (r902467)
   * fix mergeinfo miscalculation during 2-url merges (issue #3648)
   * disable custom file mutexes on Windows (r879902, -16)
   * more improvements to 'svn merge --reintegrate' (r935631)
  * mergeinfo improvements with non-inheritable mergeinfo (issue #3573)
  * handle tree conflicts involving replacements (issue #3486)
  * avoid potential segfault with subtree mergeinfo (r36613, -15, -31, -41)
  * improve 'svn merge' performance with subtree mergeinfo (r36444)
    * "tree" conflicts now handled more gracefully (issue #2282, #2908)

I really can't tell which of these were done on the client (and thus we already have) and which were done on the server. And that keeps me from being able to usefully answer questions like, "What are the top 5 or so fixes we'll get if we upgrade the server to 1.6?" We can't get a concrete sense of stability/performance improvements we'll see, or whether merges will go better, etc. Without that information, we can't prioritize an upgrade.

Note that a lot of these relate to merges. I have no idea where the split is between the server and the client as far as merges go. Does the client say, "produce some information for me to do this merge?" and let the server go off to produce it, or does the client say, "diff this and this, and search for mergeinfo here and here, etc., and send me that so I can put it together sensibly"? I realize others on this list may be able to tell where a bug fix went in just from the descriptions, but I can't, and I suspect most users not reading this list can't tell either.


Please consider the environment before printing this e-mail.

The contents of this e-mail message (including any attachments) are confidential to and are intended to be conveyed for the use of the recipient to whom it is addressed only. If you receive this transmission in error, please notify the sender of this immediately and delete the message from your system. Any distribution, reproduction or use of this message by someone other than recipient is not authorized and may be unlawful.
Received on 2011-04-11 04:12:17 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.