Testing the latest localized version for Firefox 3.5
I posted this to the Mozilla L10n newsgroup, but for maximum coverage, I’ve reposted it on my blog. Special thanks to Marcia, Axel, and Chofmann the various resources I reference below.
——————————————–
To all of our great community localizers and testers…
Over the past few weeks, many of our Mozilla community members have done testing and landed fixes for Firefox 3.5 as we close in on our release. We are now in the last hours before we ship our release candidate that we can comfortably call Firefox 3.5. If you have time this weekend, it is a great opportunity to do some last minute testing for your localization.
Where to download the latest localized nightly version of the Firefox 3.5
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1-l10n/
Please hammer on these builds mercilessly to make sure that things work well. If you notice things that worked in Firefox 3.5 beta 4, but do not work in this release, we would like to know about it right away.
What to Test
You can run a set of localization test cases by going to Litmus, Mozilla’s testing suite. This URL will take you to the “l10n run”.
https://litmus.mozilla.org/run_tests.cgi?test_run_id=36
If you don’t have a Litmus account, you should be able to create one quickly. Please email us if you need any help.
How to report feedback
Please try filing a bug for your locale with Bugzilla. The basic set of instructions are below. If you are not comfortable filing a bug, you can report it to your locale leader who should be listed in the specific locale on this main Teams page:
https://wiki.mozilla.org/L10n:Teams
Things to remember when filing a bug in https://bugzilla.mozilla.org/:
- Always include the Build ID that you tested on. If you type about: in the URL bar, this will give you the Build ID.
- Always include clear “Steps to Reproduce” the bug.
- Always check to see if your bug has already been filed. This link will help: http://tinyurl.com/2465be
- Use the regression keyword if it indeed a regression from a previous release. And, please tell us in the main comment of the bug if it is a regression from a previous release.
- If you happen to crash, please include the Breakpad ID in the bug. You can get this by typing about:crashes in the URL bar.
If you don’t wish to file a bug, report issues through http://feedback.mozilla.org or through the mozilla.feedback.firefox.prerelease newsgroup (I just linked to the Google Group). However, we prefer bugs as feedback since those are easier to track.
Finally, keep in mind that no comments or questions are off limits. Please send along any remarks or questions that you think are appropriate at you test. It’s all appreciated.
Thanks to all of you for helping test Firefox and making it the browser of choice for millions and millions of people all over the world!
Those builds still don’t update themselves though, right?
Greg, You’re right, those builds don’t update themselves. We’re working on that.
Seth, could you please tell me when will the Firefox 3.5 RC1 be ready to download? Many thanks!
Hi Gabriela: I think we’ll start to see some builds coming late on Sunday and the RC1 candidates will be posted early next week. Please stay tuned and sorry for the delay. Some blocker bugs are still getting worked out.
Hi Seth, many thanks for your quick reply! Should there be any builds coming late on Sunday, will I be able to try them? Where will I be able to download them from? Where will I be able to download the RC1 candidates from? Many thanks again!
Hi again, You should be able to download them from our RC1 site that will go live when the builds are ready. Check back early next week, or try a search with the terms “Firefox 3.5 RC1 download”. You should see in that list of results a mozilla.com site with all the versions available for download. Comment again on this blog if you need any more help.
Hi Seth, many thanks again! Could you please tell me your RC1 site’s URL for builds and candidates? Many thanks again!
I’ll post it here when it is ready. I don’t know it yet.
Ok, I’ll be looking forward to your posts then. Many thanks for all your answers!
Hi Seth, any news about the RC1 builds or candidates? Many thanks!