The future of commit access policy for core Firefox

Jean-Yves Avenard jyavenard at mozilla.com
Tue Mar 14 23:10:08 UTC 2017


> On 12 Mar 2017, at 9:40 pm, Ehsan Akhgari <ehsan.akhgari at gmail.com> wrote:
> And I still don't understand what the proposal means with rebases in
> practice.  What if, after automation tries to land your change after you
> got your final r+ the final rebase fails and you need to do a manual
> rebase?  Do you need to get another r+?  What happens if you're touching
> one of our giant popular headers and someone else manages to land a
> conflict while your reviewer gets back to you?


+1, this is a very common scenario for me…

/me just loves when a new set of “rules” are put in place to prevent a problem that has never existed so far and will be a hindrance to everyone in the future.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://mail.mozilla.org/pipermail/firefox-dev/attachments/20170315/9d5cedd4/attachment.p7s>


More information about the firefox-dev mailing list