If blocking M9 will help get swing/set crashes fixed, then I would
vote to block. I ran tests last night, but haven't been able to match
them up yet. Been busy with life recently.
Sent from my iPhone
On Mar 13, 2009, at 5:59 AM, Sian January <sianjanu...@googlemail.com>
wrote:
It should be the end of code freeze today but I'm not sure we're ready
to vote on M9 yet without discussing all of the test failures that
people have found.
It seems like the HttpURLConnection tests are test errors rather
than bugs.
I also think that if something fails on Windows Vista and not on XP
then we probably shouldn't consider it a blocker, though it would be
nice to fix it in general.
For awt and swing crashes, I think these are common (I don't think
Churong runs them as part of the integrity test suite) and have been
allowed through in previous milestones, so I don't think these are
blockers for M9.
Can anyone else offer opinions any of the other issues?
Thanks,
Sian
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with
number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU