<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">
<pre class="moz-quote-pre" wrap="">Hello,
The Nightly version number increase has landed on mozilla-central and the
soft freeze is now complete.
Thanks,
Pascal</pre>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 27/04/2020 à 11:10, Pascal Chevrel a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:907b196c-782b-c109-8181-0473e15e341b@mozilla.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi all,<br>
<br>
With Firefox 76 RC shipping soon, we are nearing the end of the
Nightly 77<br>
cycle.<br>
<br>
In order to avoid invalidating the testing we get out of late
Nightly and<br>
to ensure that we can roll out Beta 77 to a wider audience with
confidence,<br>
we'd like to ask that any risky changes be avoided from Thursday
April 30<br>
until after the version bump to 78 on May 4.<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<br>
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<br>
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<br>
cycle<br>
- Plan to kick off new experiments that might impact a feature's
merge<br>
readiness<br>
<br>
Please let us know if you have any questions/concerns.<br>
<br>
Thanks,<br>
Pascal & the Release Management team </blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Pascal Chevrel
Firefox Release Manager
+ Firefox Nightly community management</pre>
</body>
</html>