https://wiki.mozilla.org/Releases/Firefox_3.5b4 shows 3 remaining
blockers to be fixed before cycling off to build team. Once build
candidates are out, we'll move toward the beta 4 testplan.
*Here's where you can help:* Mozilla QA will cover the litmus
regression tests, but we are in need of more content testing (affected
by tracemonkey fixes), performance testing, crash testing, and new
feature testing from people. We are still hoping to release b4 before
next monday, but we want to ensure this beta is quality driven.
Check out
https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/Beta4#Additional_Resource_Testing
for specifics. This is a running list of risk areas that have
high-regression impact to newer landed areas in need of more test
coverage. *If you have recently fixed a fixed1.9.1 bug,* i am seeking
out advice on any high-risk areas of your fix that you would like extra
regression tests around. (For example, the upcoming fix for
https://bugzilla.mozilla.org/show_bug.cgi?id=475864 calls for more user
testing around default video controls and file input handling)
So grab a 1.9.1 nightly build, reply here if you have questions or
thoughts. We want to ship this beta in the highest quality we can.
Thanks,
Tony
Tony Chung wrote:
> Hello there,
>
> For those interested, here's an update on Firefox 3.5 beta 4.
>
> As of this moment, there are no beta 4 builds ready. The P1 b4 blocking
> list still has 12 bugs opened: http://snurl.com/fvzvs, where 9 of those
> are tracemonkey bugs that would still need a fix and a merge as well.
>
> Please continue to standby on builds, but keep verifying that fixed
> buglist. We'll readjust our release schedule, but the testday scheduled
> should still happen. Keep your eyes on the b4 release wiki for the
> latest: https://wiki.mozilla.org/Releases/Firefox_3.5b4
>
> Please also test the 1.9.1 branch nightly builds as hard as you can.
> Over the weekend, the nightly was crashing pretty heavily just surfing
> around various day to day websites. In particular, look for any
> regressions from fixes in bug 488421, 488015.
>
> More later as i hear it.
> Tony