The second release of Firefox 3.0 has the issues on the server.
Firefox 3.0 Release Candidate 2 (RC2) fixed about 40 bugs identified after Mozilla issued the first release candidate three weeks ago. Among the higher-profile patches added to RC2 was one that addressed a performance problem in Firefox for Linux.
Mozilla made the decision to go with another release candidate last week - rejecting the option of shipping Firefox 3.0 as is, then following up with a bug-fix update later. Mozilla executives assured users that the additional RC would not delay the expected launch date, which has been set for mid-June.
Previously, Mozilla has said it needs at least a week between issuing a release candidate and - assuming no major problems crop up - calling that build final and starting to ship Firefox 3.0.
Although all the bugs uncovered during RC1 testing have been fixed, several outstanding issues remain, according to Bugzilla, Mozilla’s bug-tracking database and management system.
But none are in the browser itself, confirmed Mike Beltzner, Mozilla’s lead developer. “[They're] all server-side and website related,” said Beltzner in an email Wednesday afternoon. “And I should note that ‘bug’ in our parlance really means ‘to-do.’ It’s our way of tracking issues.” The remaining bugs will be handled before the browser ships, he promised.
One of Mozilla’s to-dos concerns Firefox’s online help and support, which for Firefox 3.0 will be handled by the company’s support.mozilla.com domain. “That’s awaiting resolution as our IT and WebDev teams work out the best way to handle the traffic,” said Beltzner in reply to questions about the bug.
Some developers had expressed concern last month that the online help pages took too long to render. Beltzner, in fact, said last week on Bugzilla that, “Well, we damned sure can’t ship with what we have right now. Hit F1 and tell me if you think that’s good enough.”
