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

Re: maunal WC upgrade test fallout

From: Branko Čibej <brane_at_wandisco.com>
Date: Fri, 02 Nov 2012 14:07:37 +0100

On 02.11.2012 04:34, Stefan Sperling wrote:
> On Fri, Nov 02, 2012 at 02:59:10AM +0100, Stefan Sperling wrote:
>> I went ahead and disabled auto-upgrades in r1404856.

During the SVN Live conferences I asked people, privately, about their
opinion on automatic vs. manual upgrades. The overwhelming response was
that they wait for all the clients to catch up before upgrading. Given
these results, my opinion leans towards leaving auto-upgrades on, but
spending more effort on documenting that there's no way back.

Regarding read-only access to old-format WCs: I studied the
implementation and came to the conclusion that it's not worth the
effort. There's no clear connection between read-only operations and
actually not modifying the wc.db, so unless someone wants to refactor
the WC code (and all the bits that rely on it) again, this is not going
to happen.

> This caused some test fallout which should be mostly fixed now.
> The main issue was that I temporarily broke most of the tests
> when run within a 1.7 WC.
>
> The only remaining issue I'm aware of is that upgrade_tests.py
> ends up upgrading the parent WC during the test run. I'm not quite
> sure yet what we can do to prevent that.

Sounds like a bug in either the test code, or the bits of wc-ng that try
to determine the wc root...

-- Brane
Received on 2012-11-02 14:08:19 CET

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