<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 22/08/2018 21:29, Mark Banner wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3e79d91a-ad3f-2906-a1ec-96e9e22d0ff9@mozilla.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>Since there are a large amount of instances (approx 12k) that
would need to be fixed across the code base, I would propose
that we roll it out on a per-directory basis. For example, we
could do all of browser/ at the start of the 64 cycle just after
the merges (alternately the end of the 63 cycle during soft
freeze), then do toolkit/ at the next merge time, and then pick
up the rest at the end. This will limit the scope of possible
bitrotting to smaller chunks, as well as making the patch sizes
more manageable.<br>
</p>
</blockquote>
<p>I've not heard any negative comments, so I am moving forward with
this. Having looked at the stats a bit more, I'm going to land
this in two chunks. The first will be to enable the rule on files
in these sub-directories of mozilla-central:<br>
</p>
<p>browser/ services/ toolkit/ taskcluster/</p>
<p>I'm aiming to land these on Friday (31st August), ahead of the 63
merges to beta. As others suggested, this should make uplifts
easier. <a moz-do-not-send="true"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1486739">Bug
1486739</a> is tracking this.</p>
<p>For the rest of the files, I'm currently looking at Friday 19
October, ahead of the 64 merges to beta. <a
moz-do-not-send="true"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=1486741">Bug
1486741</a> will track this part.</p>
<p>Mark.<br>
</p>
</body>
</html>