What happend to 2.2.2

[Tim Potter]

Esh, Andrew writes:

> I think we should be prepared to wait for a while for 2.2.2, even after the
> winbindd memory leak fixes are checked in. The amount of code being changed
> is significant, so there are bound to be some bugs and side effects. I
> period of testing is needed before we can be sure the new code isn't causing
> serious problems.
> 
> I am heavily focused on winbindd memory leaks, from a testing standpoint, so
> I will provide feedback as soon as I can.

Thanks.  You are right though - I think the winbindd changes are
just too big to be put in 2.2.2.  It usually takes a while to
work out all the strange corner cases for domain controller
failures.


Tim.