Platform/2011-02-01

« previous week | index | next week »

Notices / Schedule

Firefox 4

Firefox 3.6.14 and 3.5.17

Firefox 3.6.15 and 3.5.18

Blocker Report

Firefox 4 Beta

• http://blocker-reports.brasstacks.mozilla.com
  • 39 nominations need triage
  • 10 blockers need prioritization
• http://office.smedbergs.us/blocker-report/

Blocker report for Firefox 4.0.betaN (as of 2011-02-01 10:37:33.617400-08:00)

Overview
----------------------------------------------

4.0.betaN
                blocking: 1703

                   fixed: 1589

                    open: 114
                   has patch:  73
                    no patch:  41

       open hardblockers:  33
                   has patch:  28
                    no patch:   5

       open softblockers:  64
                   has patch:  35
                    no patch:  29

    uncategorized blockers:  17
                   has patch:  10
                    no patch:   7

Outstanding Review Requests
----------------------------------------------

                     brendan@mozilla.org:   5 +++++
                   gavin.sharp@gmail.com:   4 ++++
                         dao@mozilla.com:   3 +++
                   honzab.moz@firemni.cz:   2 ++
                       roc@ocallahan.org:   2 ++
                       joshmoz@gmail.com:   2 ++
                 jones.chris.g@gmail.com:   2 ++
                         jst@mozilla.org:   2 ++
                      dolske@mozilla.com:   2 ++
                                            ...

Firefox Development

• Of 78 total hardblockers, only 14 remain, with 11 of those being beta hard blockers.

GFX

• 8 hardblockers

Stability Report

• Beta10 - Top crasher Bug 628152 was under the radar in early Beta10 testing, then exploded. Fixed for Beta11.
• Trunk - Some stability issues mostly due to Bug 629912. Now fixed. A couple of other regressions due to additional accessibility fixes.
• Missing symbols for some crash signatures - A problem introduced when we moved the Sicorro data center to Phoenix. The solution for getting the build symbols to Phoenix is not performing (taking 15 hrs). Many signatures like xul.dll@0x189e71 scattered in crash reports. No visibility into what the crashes are - risks there.
• Although we are doing well stability-wise for FF4, we are tracking all the crash signatures that are new to FF4 and not in 3.6.13 and their status. We have already determined we cannot fix some of these but still worth keeping on the radar since we don't know what will happen when we release. We may need to provide some emergency fix for something. https://wiki.mozilla.org/CrashKill/Firefox4#Crash_Regressions_From_3.6.13

Roundtable

• Should we take bug 355178 on beta 11? (ehsan)
  • An analysis of the risks and benefits is available here.
  • We need this for beta 11 if we decide to take it for 2.0.