The only bug that is left on the radar is an unconfirmed issue:
https://bugzilla.mozilla.org/show_bug.cgi?id=354414
As far as I am aware every other known issue is wrapped up. If you
know of anything else that should block FF2/RC2 let's hear it.
Otherwise we should start spinning en-US later tonight.
Best,
Schrep
http://news.com.com/2100-1002_3-6121608.html
Any possibility of having the claim validated at least before FF2 is
released.
It would really hurt the image of FF, if something like this hasn't
been at least validated (& fixed) before a major release hits the
streets.
I'm not an expert on javascript.
But would be more than willing to help out with any testing, given
proper guidance on what needs to be done.
Kind regards,
-kcs
Thanks for you offer to help test.
If the reported issue is a problem we'll definitely address it as fast
as possible. Unfortunately the little bit of info we do have
(https://bugzilla.mozilla.org/show_bug.cgi?id=355069) doesn't give us
enough information to understand yet how big an issue this is.
We'll likely spin RC2 in parallel as we continue to investigate.
Cheers,
Schrep
> Otherwise we should start spinning en-US later tonight.
en-US builds are now available in:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2.0rc2-candidates/rc1/
Expect l10n and source tarball bits later today after the update to bug
353341 get reviewed/lands.
Thanks!
Later,
preed
--
J. Paul Reed
Build/Release Engineer - The Mozilla Corporation
smtp://pr...@mozilla.com
irc://irc.mozilla.org/preed
pots://650.903.0800/x256
> Expect l10n and source tarball bits later today after the update to bug
> 353341 get reviewed/lands.
l10n bits are now available for testing as well.
I'll be running the metadiff tools/report tomorrow.
QA is working up an estimate of the effect to the planned RC 2 release
date, and preed will announce when the new bits become available.
cheers,
mike
http://news.zdnet.com/2100-1009_22-6122317.html