> Has this been files as a bug yet? It's for sure confirmed, only question > is if we'll figure it out soon enough to merit waiting on 2.0.1. Paul has > a couple of fixes he wants to hold 2.0.1 for, but I'd prefer to avoid > doing that too often.
I filed it as bug #119 yesterday. I think we should release 2.0.1 now, and not wait. We already have fixed a lot of bugs, and nobody says we have to wait a minimum time before 2.0.2 can be released. 2.0.2 can be released as soon as these bugs are fixed. I'm happy with using 2.0.1 instead of 2.0.0 for now, it is better and has no known regressions as far as I can see. -=Dead2=-
