tdb_chainlock() in tdb1, tdb2 and tdb_compat ?

[Volker Lendecke]

On Fri, May 11, 2012 at 07:24:20PM +1000, Andrew Bartlett wrote:
> On Thu, 2012-05-10 at 08:40 -0400, simo wrote:
> > On Thu, 2012-05-10 at 13:49 +0200, Christian Ambach wrote: 
> > > On 05/10/2012 07:33 AM, Rusty Russell wrote:
> > > 
> > > > Or we could just remove tdb1, as I planned, which will force us to fix
> > > > any issues.
> > > 
> > > Who would deal with the required additions to the autoconf build?
> > > You expressed some concerns about your ability to do that in the past.
> > > 
> > > > The API confusion which caused Volker to start this thread is due to my
> > > > slow transition.
> > > 
> > > Is there an ETA until when the transition could be finished? I still see 
> > > this as a blocker for the Samba4 beta release.
> > 
> > +1
> 
> I agree this is an important issue, but is there a reason to block the
> beta release based on it, except to try and draw attention to the issue?
> We do not currently have a regression in this area, and there will be
> plenty of beta releases beyond this one to sort this out into.
> 
> We certainly should, now Rusty is back on board, set some deadlines for
> sorting this out, but I don't think we should tie this internal
> technical transition it to particular releases that our users can
> otherwise test and enjoy. 

By moving vom alpha to beta with this known issue in we are
making a statement that we are blessing the code as it
stands. Further alphas, sure, a beta, I don't know.

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de