BDB deprecation (was: branch 1.8 or at least start making alpha releases?)

On 02/14/2013 10:23 PM, Branko Čibej wrote:
> On 15.02.2013 04:19, Branko Čibej wrote:
>> There are other new features in 1.8 that would benefit from having
>> potential users (and packagers) look at them sooner rather than later.
>> So I'm firmly in the "release alpha from trunk now" camp.
>
> And let's not forget that releasing anything but an alpha is blocking on
> the Serf 1.2 release, see
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=4296

FIXED.

> and IMHO a resolution to the "deprecate Berkeley DB" discussion.

My current thoughts on this can be summarized like so:

* The appropriate time to stop supporting Berkeley DB is in the same release
for which existing FSFS will also have to dump/load. It is cruel to force
admins to endure the migration process twice -- possibly in successive
releases of Subversion -- and especially when one of those times is just for
a (possibly less-than-compelling) bit of a performance boost.

* That said, I'm okay with deprecating Berkeley DB today as a warning to
existing BDB users that change is a-comin', though the release notes should
(again) indicate that there's no reason to rush off and convert to FSFS
until an as-yet-undecided future revision forces the issue for *all*
Subversion users.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development