Firefox 4 Beta 5 candidate available for testing!

Marcia Knous marcia at mozilla.org
Tue Sep 7 17:21:55 PDT 2010


Once again, warm greetings to all of our great community testers - you 
are our most valuable resource. We now have a *Firefox 4 Beta 5 
candidate* available for testing. Note that this build is a development 
build and is intended for pre-release testing. We would like your help 
in testing the build and identifying any possible regressions or issues. 
You can read all about the release here: 
http://www.mozilla.com/en-US/firefox/beta/

*What to Test/Where to Get Builds: *

*Please see http://www.mozilla.com/en-US/firefox/all-beta.html - there 
are direct links to the builds on that page.

Please hammer on these builds mercilessly to make sure that things work 
well!

Read the Release Notes
* Please also make sure to read the Release Notes 
<http://www.mozilla.com/en-US/firefox/4.0b5/releasenotes/> which detail 
the known issues and describe the complete list of changes in this 
version.  *Mac users* may want to pay particular note to the following 
bugs since they were not present in Beta 4:
** Mouse/keyboard events sent to plugin while in background tab, in 
Cocoa event mode - https://bugzilla.mozilla.org/show_bug.cgi?id=592563
** Screen artifacts scrolling, and switching tabs from, pages containing 
(Flash) plugins - https://bugzilla.mozilla.org/show_bug.cgi?id=592453

*Some cool things to try:
** Windows 7 Users only: Try out the sites listed at the bottom of this 
page: https://wiki.mozilla.org/Platform/GFX/Direct2DDemo
** Try out Firefox Panorama!
** Try out Firefox Sync!
** Try out the Feedback button!
** Make sure to go to Mozilla Plugin Check 
<http://www.mozilla.com/en-US/plugincheck/> to verify you are running 
the latest version of Flash and other plugins.

*How to Report Feedback:*
(1) File a bug in https://bugzilla.mozilla.org/. *Note in the comment if 
it is a regression from a previous release. Things to remember when 
filing a bug:
(a) Always include the Build ID that you tested on. If you type about: 
in the URL bar, this will give you the Build ID.
(b) Always include clear Steps to Reproduce the bug
(c) Always check to see if your bug has already been filed. This link 
will help: http://tinyurl.com/2465be
(d) Use the /regression/ keyword if it indeed a regression from a 
previous release.
(e) If you happen to crash, please submit your crash information! This 
helps us continually improve the product. Please also include the 
Breakpad Crash ID in the bug. You can get the crash ID by typing 
about:crashes in the URL bar.
(f) If you tend to run with lots of extensions, try starting Firefox in 
Safe Mode before filing to bug to see if the problem persists. Info 
about safe mode is here: http://support.mozilla.com/en-US/kb/Safe+Mode

(2) If you don't wish to file a bug, report issues through the Firefox 
Feedback button, http://feedback.mozilla.org or through the 
mozilla.feedback.firefox.prerelease newsgroup (also available on Google 
Groups). However, we prefer bugs as feedback is easier to track.

Thanks in advance to all of you for helping test Firefox and making it 
the browser of choice for millions of people all over the world!

marcia, on behalf of
Team Mozilla QA




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/nightly-testers/attachments/20100907/eb8e1c04/attachment.html>


More information about the Nightly-testers mailing list