Hi all,

On March 1st, we will be merging Firefox 60 from mozilla-central to beta
for the first time.  In order to avoid invalidating the testing we get out
of nightly and the early Developer Edition builds and to ensure that we can
roll out beta60 with confidence, we'd like to ask that any risky changes be
avoided from March 1st until the version bump to 61 on March 12.

Dos and Don'ts during the soft code freeze:

   - Be ready to backout patches that cause crash spikes, new crashes,
   severe regressions

   - Monitor new regressions and escalate merge blockers

   - Support release management by prioritizing fixing of merge blockers

Do Not:

   - Land a risky patch or a large patch

   - Land new features (that affects the current nightly version) — be
   mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead
   to unexpected CI results

   - Flip prefs that enable new Features that were untested in Nightly cycle

   - Plan to kick off new experiments that might impact a feature's merge

Please let us know if you have any questions/concerns.

Release management team
dev-platform mailing list

Reply via email to