MozillaZine

Mozilla Firefox 2.0.0.4 and 1.5.0.12 Community Test Day on Friday

Thursday May 3rd, 2007

The Mozilla Quality weblog has announced a Mozilla Firefox 2.0.0.4 and 1.5.0.12 Community Test Day tomorrow. The Community Test Day will allow interested members of the Mozilla community to test release candidates of the upcoming Firefox 2.0.0.4 and 1.5.0.12 releases. The Mozilla Wiki has a page with full details about the Firefox 2.0.0.4 and 1.5.0.12 Community Test Day, which will take place on Friday between 7:00am and 5:00pm Pacific Daylight Time (2:00pm and 12:00pm UTC/GMT).

The weblog announcement also features an appeal for volunteers to join a Mac-specific testing list, in anticipation of the release of Mac OS X 10.5 Leopard later this year.


#1 What has changed

by SomeGuy

Thursday May 3rd, 2007 7:09 PM

Reply to this message

I didn't see a change log there, what has changed? And I am curious why a public testing day is deemed to be needed.

#2 Re: What has changed

by SomeGuy

Thursday May 3rd, 2007 7:23 PM

Reply to this message

Hmmm... Something has changed significantly apparently. Just tried grabbing the 2.0.0.4 RC build from that page and it is refusing to load under NT 4 (The procedure entry point GetLongPathNameA could not be located in the dynamic link library KERNEL32.dll) BTW, 2.0.0.3 works fine (using that now!)

#4 Re: Re: What has changed

by schapel

Friday May 4th, 2007 5:50 AM

Reply to this message

Make sure you report the bug, as you found exactly the kind of problem they're looking for with the testing. As for a changelog, probably nearly nothing has changed except for bug fixes: <https://bugzilla.mozilla.…-0-0=noop&value0-0-0=>

#3 Testing Day is nothing new

by Kelson

Thursday May 3rd, 2007 7:54 PM

Reply to this message

If you look through the archives at the Mozilla QA blog -- <http://weblogs.mozillazine.org/qa/> -- you'll see that there's been a community test day for each Firefox point release going back... well, quite a while. The idea is to get more people hammering away at it than just the usual nightly testers so that they can catch anything that's stopped working before the update goes out.

The news just doesn't always make it to the front of Mozillazine.