<html><head></head><body>I like this idea. I'm pretty sure we trust the folks with review permissions these days, and like you said, a- on trunk is rare.<br><br><div class="gmail_quote">On August 27, 2015 7:33:43 PM EDT, Gervase Markham <gerv@mozilla.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">I'd like to propose we remove the approval requirement for trunk.<br /><br />LpSolit said the last time he can remember anyone a-minusing a patch for<br />trunk was where the feature wasn't actually wanted, and no-one had<br />bothered to point this out, and it was quite a few years ago.<br /><br />If we instead had some sort of last resort "the project lead can request<br />a backout of a trunk feature if he decides it's not actually wanted"<br />power, and expect that power to be used about once every 5 years, would<br />that be enough to eliminate this extra bureaucratic step?<br /><br />The one exception, I suggest, would be for patches which touch the DB,<br />which can not be so easily backed out. Those would continue to require<br />approval from an approver.<br /><br />Approval would also remain in place for stable branches, where approvers<br />are supposed to weigh the importance of the patch against the risk to<br />stability.<br /><br />What do
you
all think?<br /><br />Gerv<br /><hr /><br />dev-apps-bugzilla mailing list<br />dev-apps-bugzilla@lists.mozilla.org<br /><a href="https://lists.mozilla.org/listinfo/dev-apps-bugzilla">https://lists.mozilla.org/listinfo/dev-apps-bugzilla</a><br />-<br />To view or change your list settings, click here:<br /><<a href="http://bugzilla.org/cgi-bin/mj_wwwusr?user=justdave@bugzilla.org">http://bugzilla.org/cgi-bin/mj_wwwusr?user=justdave@bugzilla.org</a>><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html>