Michael Pilato wrote:
>> I submit that this is not a new feature, but is essentially a
>> bugfix for all those wedged-repository bugs we've seen, and is therefore
>> a valid candidate for a patch release. There are of course no API
>> changes involved.
>>
>
> I agree that this is 1.3.1-able. But I would caution against an overly
> quick release of this code. News of BDB 4.4 support will be welcomed by
> Subversion users everywhere, and we want to make sure that the hype is
> backed by soundly tested code.
>
> Would you (or anyone else) object to our running an RC cycle (maybe two
> weeks) for the 1.3.1 release, during which time I can get svn.collab.net
> running BDB 4.4 and subversion-1.3.1-rc1?
We can easily wait several weeks, it's not as if that code has a
particularly short half-life...
> For kicks I could even write
> a cron job on that box that runs a binary which opens the repository and
> then abort()s. :-)
>
And you don't even have to write such a binary... it's called "svnadmin
crashtest". :)
>> BTW, is issue 2449, and fixing it will produce minor collateral damage
>> by incidentally closing issues 688, 739 and 2019.
>>
>
> Shucks. What a bummer.
>
Yup.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 14 18:24:57 2006