Emergency checkin procedures

[David Miller]

Myk and I have both been a bit hard to find lately.  Approvals are 
getting done, but it often takes a few hours to a day or two.

There's been at least one case recently where the tree was outright 
broken for a while because of a regression and the fix for the 
regression didn't get approved immediately.

Since we like to try to keep the tree stable, I'm going to try a little 
bit of an experiment here.

If you have a situation where the trunk is broken and it causes dataloss 
or prevents Bugzilla from being usable, backing out the patch that 
caused it is not workable due to subsequent checkins or data conversion 
that's already been done, and you can't find someone to approve the 
patch to fix it in a timely manner, get two reviewers to agree to it, 
and then go ahead and check the fix in.  Please leave the approval flag 
requested on the bug, as it'll still need to be checked for approval 
retroactively, and make sure to justify in comments in the bug why you 
needed to proceed with the checkin.

Please only do this when it really is a critical regression.  Situations 
where this permission is utilized will get reviewed, and if I find 
people abusing it, this permission will go away.

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/