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

Re: Greetings from Sleepycat

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-09-20 17:29:36 CEST

Gregory Burd <gburd@sleepycat.com> writes:

> I'm Greg, I work for Sleepycat. We make Berkeley DB, but then
> you already knew that. We consider Subversion's use of DB strategic
> and we'd like to make sure that you and the users of Subversion are
> happy with DB. To that end, we are in the final stages of testing a
> new release of DB, 4.3.x, and we'd like to test it out with you before
> we release it. If someone would volunteer to test it against
> Subversion I'll send them the URL for release candidate. Also, I've
> opened a support request to track a database corruption issue. We're
> confident that a closer partnership will help eliminate those issues
> and better integrate DB into Subversion. I've subscribed to this
> email list and you'll find me lurking on #svn-dev and #svn as
> 'gregburd', feel free to say hi.

Pleased to meet you, Gregory.

As I'm sure you're aware if you've been lurking for any significant
amount of time, the general sense around here is that Berkeley DB
works wonderfully as long as you play by the rules. Unfortunately,
the rules are somewhat restrictive (but in ways that Subversion itself
could alleviate). And then there is the occasional report by someone
who swears up and down they've played by all the rules and still their
BDB-backed repositories are getting trashed.

At any rate, a close(r) partnership between the Sleepycat folks and
our community here can be nothing short of a good thing, so on behalf
of all the developers here, "Welcome."

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 20 17:31:28 2004

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.