That was my intent, indeed. BTW we still want to cut 0.4 soon. The issue list is shrinking but still about 10 out there. Let's lean more and more towards pushing issues out if not done in a day or two, and lean towards tying up any loose ends now.
(That is also to say, I don't think new classifiers belong in 0.4.) On Mon, Sep 27, 2010 at 2:54 AM, Drew Farris <[email protected]> wrote: > On Sun, Sep 26, 2010 at 7:48 PM, Sean Owen <[email protected]> wrote: >> No, I just meant it would be better to deprecate than remove it. And >> deprecation can come later. Better still to make it all >> backwards-compatible as is possible. >> > > It would be great to deprecate the existing bayes code >post< 0.4 -- > the new vector bayes code is certainly coming into being very close to > the 0.4 release. How about considering new vector-based bayes code > experimental for the 0.4 release, with the goal of fully certifying it > for the 0.5 release and deprecating the existing bayes on 0.5. >
