> I'm not going to wait very long even for this bug, though. Instead, I'm
> going to get 4.0.0 out the door, and move on to 4.0.1, sticking as close
> to the announced schedule as possible.
FWIW the recent Java failures have been fixed (thanks to the Java hackers!) on
SPARC, so the 4.0.0pre comp
I plan to create RC2 bits tomorrow.
The only PR which I currently think might merit holding up the final
release is:
20973 [4.0/4.1 Regression] kdelibs (khtml) miscompiled by reload
Michael Matz has attached a possible reload patch to the PR. Any comments?
I'm not going to wait very long even fo
