-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 21, 2008, at 2:16 PM, Brett Cannon wrote:
But waiting until all the betas have gone out totally defeats the purpose of the betas! It has already been stated that new code changes that are even remotely shaky or anything not small needs a code review at this point since we only have one beta left. Barry can correct me if I am wrong, but dropping a major rewrite of bsddb into 3.0 between b3 and rc1 is not acceptable. I wouldn't be surprised if all code after b3 requires a code review since at that point we should just be squashing bugs, not rewriting code. And if you are migrating all of bsddb3 at once then that is going to be a massive code review that should be happening in prep for rc1.
I agree. Our last beta is scheduled for this wednesday and if we have any hope of hitting our Oct 1 target, we really can't afford to slip. I'll just state that I'm going to be even more conservative about what gets in after b3. I'd say that if you expect it to go in to Python 2.6 or 3.0, you better get it in now.
I really hate feeling like I am coming off as a jerk harping on this, Jesus, as I don't want to discourage your contributions to pybsddb, but it just doesn't feel reasonable to me to be doing this so late in the release cycle.
Let's however try to find a way to let Jesus and others continue to work on important tools like bsddb even if it can't make it into the final releases. Perhaps we can move this stuff to the sandbox and setuptools-ify it.