<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">The subject should have been "Soft code
freeze for Firefox 74 starts February 4" of course, not 73, sorry
for the inconvenience.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Pascal</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 04/02/2020 à 14:00, Pascal Chevrel a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:3c918626-cc7c-82a6-fa72-4ec1a6a2e5b9@mozilla.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>Hi all,<br>
<br>
With Firefox 73 RC shipping today, we are nearing the end of the
Nightly 74 cycle.<br>
<br>
In order to avoid invalidating the testing we get out of late
Nightly and to ensure that we can roll out Beta 74 to a wider
audience with confidence, we'd like to ask that any risky
changes be avoided from today until after the version bump to 74
on February 10.<br>
<br>
Some reminders for the soft code freeze period:<br>
<br>
Do:<br>
- Be ready to back out patches that cause crash spikes, new
crashes, severe regressions<br>
- Monitor new regressions and escalate merge blockers<br>
- Support release management by prioritizing fixing of merge
blockers<br>
<br>
Do Not:<br>
- Land a risky patch or a large patch<br>
- Land new features (that affect the current Nightly version) —
be mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA
ifdefs can lead to<br>
unexpected CI results<br>
- Flip prefs that enable new Features that were untested in the
Nightly cycle<br>
- Plan to kick off new experiments that might impact a feature's
merge readiness<br>
<br>
Please let us know if you have any questions/concerns.<br>
<br>
Thanks,<br>
Pascal & the Release Management team<br>
</p>
<pre class="moz-signature" cols="72">--
Pascal Chevrel
Firefox Release Manager
+ Firefox Nightly community management</pre>
</blockquote>
<p><br>
</p>
</body>
</html>