Mozilla have released the latest beta version of popular open-source browser Firefox for testing today.<\/p>\n
The most notable change in this version is the increment in version numbers from 3.1b3 to 3.5b4. As noted in my previous post<\/a> this is due to the inclusion of a number of significant bug fixes and additional features to the code base. For those interested in downloading and testing this new version, here is the beta release email.<\/p>\n Greetings to all of our great community testers – you are our most *What to Test\/Where to Get Builds**:*<\/p>\n (Note: If you are riding the “beta” channel, you can manually check for http:\/\/www.mozilla.com\/en-US\/firefox\/all-beta.html<\/span><\/a><\/p>\n Please hammer on these builds mercilessly to make sure that things work Read the Release Notes ***_How to Report Feedback_:*
\nThis latest beta includes updates to TraceMonkey<\/a>, Firefox’s Private Browsing Mode<\/a> and also support for more CSS and HTML5 attributes. You can read a full list of updates in the beta release notes<\/a>.<\/p>\n
\nvaluable resource. We now have Firefox 3.5 Beta 4 available for testing
\n(Note: Since my last missive, we have changed the release name to
\nFirefox 3.5, the release formerly known as Firefox 3.1). Note that this
\nbuild is a beta and is intended for pre-release testing. We would like
\nyour help in testing the release and identifying any possible
\nregressions or issues.<\/span><\/p>\n
\nupdates and update to this build). Otherwise you will have to download
\nfrom the directory below.<\/p>\n
\nwell! If you notice things that worked in Firefox 3.1 Beta 3 and do not
\nwork in this release, we would like to know about it right away.<\/p>\n
\n*Please also make sure to read the Release Notes which detail the known
\nissues: http:\/\/en-us.www.mozilla.com\/en-US\/firefox\/3.5b4\/releasenotes\/<\/span><\/a><\/p>\n
\n(1) File a bug in *https:\/\/bugzilla.mozilla.org\/.<\/span><\/a> *Note in the comment
\nif it is a regression from a previous release. Things to remember when
\nfiling a bug:
\n(a) Always include the Build ID that you tested on. If you type
\nabout: in the URL bar, this will give you the Build ID.
\n(b) Always include clear Steps to Reproduce the bug
\n(c) Always check to see if your bug has already been filed. This link
\nwill help: http:\/\/tinyurl.com\/2465be<\/span><\/a>
\n(d) Use the regression keyword if it indeed a regression from a
\nprevious release.
\n(e) If you happen to crash, please include the Breakpad ID in the bug.
\nYou can get this by typing about:crashes in the URL bar.<\/p>\n