Firefox 3.1 beta 3 code freeze slated for Jan 13 -- maybe

Firefox 3.1 beta 3 code freeze slated for Jan 13 -- maybe

Summary: The code freeze for the third beta of Firefox 3.1 is scheduled for next Tuesday but could slip if Javascript bugs are not resolved soon.

SHARE:

The code freeze for the third beta of Firefox 3.1 is scheduled for next Tuesday but could slip if Javascript bugs are not resolved soon.

During the team's weekly meeting, developer Rob Sayre flagged the Javascript engine blockers as a potential risk to the planned code freeze date of January 13th.  He did not know exactly how long it will take to fix the remaining issues and is expected to provide a better estimate soon. Still, he said the existing blockers could push it back anywhere up to three weeks.

Contacted after the meeting, Mozilla engineering chief Mike Beltzner said there is no "declared" slip for the schedule of Firefox 3.1 beta 3 but acknowledged the concerns raised by the developer. "If that estimate puts the code freeze date at risk, we'll make the appropriate announcements in the Mozilla developer planning newsgroups," Beltzner told this ZDNet blogger.

Beta 3 is scheduled for release on January 26.

Beta 2 -- with private browsing included -- was delivered on December 8.  The Mozilla team opted to go to a Beta 3 beta cycle rather than a release candidate last month to ensure that users had enough time to test this new feature. 

 According to Firefox team estimates, there are currently about 300,000 beta testers of Beta 2.  

Topics: Browser, CXO, Software Development

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

6 comments
Log in or register to join the discussion
  • No Problems, according to Moaillar, with Fire Fox 3.0.1

    Intresting

    Firefox will not admit on it Bug site that thre are any problems with 3.0.x

    I and most probaly a lot others are BUGGED with Firefox freezing, and having to close Firefox down, during webpage downloads attempting to restar Firefox after this type of shut down results in a message say that Firefox is already running and without being able to kill Firefox using Task Manager, no matter how hard or how many times you try the only optionn is to reeboot.

    Mozilars take on this is to balme your firewall software, the most popular to blame is Zone Alarm if you don't have firewall sofware then they blame your AV software, Users have also reported problems with Serverbase Firewall & AV software as by several Software Houses.
    Mason.Paul
    • Not 3.0.1, 3.1 Beta

      Hes not talking about the current version 3.0.x. Hes talking about the upcoming 3.1 versions. READ!! 3.0.x for me works better than that dump known as IE!!
      ericvhunter@...
    • Try Chrome instead

      I don't know why everyone is being nasty. Aparently they are more
      practiced at that than reading, themselves.

      I switched to Chrome over these very issues. When you have to
      periodically restart your browser because it has gotten bloated and
      slow (and it takes many minutes to exit as a result)--and they
      have spent years and releases trying to fix the memory leaks..

      Well, my conclusion is there is something wrong with their whole
      approach.

      I don't know the specifics of the bugs in question, but they may
      relate to this issue.

      Chrome's approach makes it more robust. Even if one tab
      encounters an issue, the rest of your sessions are intact.

      You gave to give up a lot of nice addins though. Some of which
      may have been contributing to the problem, to be sure.

      Still, must of the time I value robustness and performance over
      addins. Now I mostly just use Firefox for Firebug.
      Bob.Kerns
      • Chrome is more Google spyware

        I often have Firefox open with 40-50 tabs and have few problems. Sometimes, if I have not had time to read things, it does slow down after a couple of days. But then, I just close it, tell it to remember my tabs, and restart it. Not a big issue. I would rather live with this than give even more information about myself to Google. I would never recommend Google apps of any kind, except Search.
        jorjitop
  • RE: Firefox 3.1 beta 3 code freeze slated for Jan 13 -- maybe

    Lets see, 1 is greater than 0, so 3.1 must come after 3.0.5. Clear?
    BearPup
  • RE: Firefox 3.1 beta 3 code freeze slated for Jan 13 -- maybe

    Lets see, 1 is greater than 0. So 3.1 just has to come after 3.0.1, or the current 3.0.5 .

    If that's too much for some,... oh forget it.

    Last posted dated for public release: January 26, 2009.

    Enjoy!
    BearPup