Summary

  • The betaN softblockers will be punted out of Firefox 4 very soon
  • Please look over the betaN softblockers by THIS FRIDAY, 9:00 am PST, looking for bugs that should be upgraded to hardblocking status
  • If you find a softblocker that needs to make Firefox 4, do the following:
    1. Remove “[softblocker]” from the whiteboard
    2. Add justification to the bug
    3. Toggle the “blocking2.0” flag to “?” (aka nominate it for blocking)

Details

The betaN softblockers are bugs that have been previously identified as:

  1. really nice to have for Firefox 4 but won’t stop us from shipping (the “softblocking” part)
  2. needing beta coverage to make sure the fix is correct and doesn’t cause new issues (the “betaN” part)

Regardless if beta 12 is the last beta, we are rapidly approaching the point where there will be no more betas. Once we freeze for the last beta, non-blocking bugs that require beta coverage are implicitly no longer approved.

We ask that interested developers make sure our soft/hardblocking and beta coverage decisions are sound before we freeze for the final Firefox 4 beta. Additionally, we understand that new information may have come to light (such as reproducibility, impact, etc) and want to make sure we are making decisions with the correct data.

Please take a moment to look over the betaN softblocker list by THIS FRIDAY, 9:00 am PST, looking for bugs that should be upgraded to hardblocking status.

If you find a softblocker that needs to make Firefox 4, do the following:

  1. Remove “[softblocker]” from the whiteboard
  2. Add justification to the bug
  3. Toggle the “blocking2.0” flag to “?” (aka nominate it for blocking)

To be warned, the bar for a hardblocker is extremely high at this point, especially for bugs that have been marked softblocking so long.

After this Friday at 9:00 am PST we reserve the right to remove the blocking status of the betaN softblockers (and thus automatic approval) at any time. Once we do so, approvals will be on a case-by-case basis.

Tagged with:  

2 Responses to Blockers, softblockers, betas and you

  1. As much as I hate such directives, I think we need a anything that is not a hardblocker for BetaN+ needs to have an explicit a= from pone person (perhaps you?). I think things are getting way out of hand now. Also I think no new bugs can be marked as Blocking BetaN+ without the same single person approving that as well. Otherwise this is just never going to be released. (Just my opinion, I could be wrong).

    • Christian says:

      We’re planning on moving to that model after we freeze for the final beta. Final softblockers will start needing explicit approval (and betaN hardblockers are deferred)