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

Re: 1.7.1 soon - Please review

From: Hyrum K Wright <hyrum.wright_at_wandisco.com>
Date: Tue, 18 Oct 2011 23:00:39 -0500

On Tue, Oct 18, 2011 at 7:20 PM, Bert Huijben <bert_at_qqmail.nl> wrote:
>        Hi,
> With the current stream of user reports of a few specific upgrade problems
> Hyrum intends to cut a Subversion 1.7.1 soon.
> I would like to see the following patches that are in STATUS to go in, but
> they need more votes:
> * r1185242: Trivial patch that resolves a common concurrency problem in
> clients that use a database multithreaded.
> Already applied by the VisualSVN team before 1.7.0 was released and
> currently about causes 60% of the AnkhSVN error reports for 1.7.0. The
> r1185280 group is needed to avoid failure in a testcase that relied on
> undocumented SQLite behavior.
> * r1185738 group: Adds the missing implementation to allow upgrading
> 'absent' nodes properly. In the open source world we don't use the authz
> features, but a lot of enterprise users do use this.
> * r1185911 group: A very simple fix that resolves a regression on updating
> sparse directories.
> * r1181609: Fixes a major regression for our api-users that perform a 'svn
> status -U' .

This was merged to 1.7.x in r1185955.

> There are a few other interesting patches in there that could also use some
> votes.

The one other issue I'd like to see resolved is Philip's work on
incomplete trees after upgrade (issue 4035). That seems to be a
common one that folks are reporting on users@, but Philip has made
some headway, and I'd really like to see this high-impact bug fixed in

> So please, start reviewing.... and/or keep those issue reports coming before
> other users encounter them :)



uberSVN: Apache Subversion Made Easy
Received on 2011-10-19 06:01:23 CEST

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

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