>From the discussion, it sounds like the release-critical aspects of this bug are fixed, and the remaining aspects of the bug are not release-critical. Downgrade anyone? :-)