Quick note about softblocking bugs:
- Blocking bugs marked [softblocker] (betaN or final) NO LONGER have automatic approval
- To land a softblocker on mozilla-central you can do one of the following:
If the risk / reward ratio is close to zero….
- Add justification to the bug
- Toggle the “approval2.0” flag on the patch to “?” (aka ask for approval on the patch itself)
-OR-
If you think the bug is wrongly categorized and needs to block the release of Firefox 4…
- Remove “[softblocker]” from the whiteboard
- Add justification to the bug
- Toggle the “blocking2.0” flag to “?” (aka nominate it for hardblocking)
- This means the ONLY bugs with automatic approval are hardblockers (betaN or final)
- We will be setting the “blocking2.0” flag to “-” shortly (aka making them not blocking)
- We will not be going through and removing [softblocker] from the whiteboard
Please let me know if you have any questions or concerns.
Congratulations on this important decision!
Okay, I m going to ask what might be a dumb question.
Many of the soft blockers may still be fixed in 4.0.x maintenance releases, right?
I’m just hoping we won’t have to wait until Firefox 4.1 or 5 or anything.
Anyway, thanks for all the hard work you and hundreds of others put into my favorite web browser/application platform thing.
Not a dumb question at all! Yes, they are eligible to making it in the .x releases and some may even land in 4.0 proper. It’s really a narrowing of scope but we are still deciding on the bugs on a case-by-case basis. Of course, evey day goes by the bar gets higher and higher to what we’d take.
Do Softblockers qualify for Blocking +.x State?
Can this be done in a Mass Change or manual Triage after Branching happened?
If no, why? š
Yes, the softblockers will be one of the first places we look for the .x bugs but we don’t want to move them all blindly. I will likely be doing a mass change, but it seems Bugzilla might foil that plan and I might need to write a quick script.