Hi all,

On April 26th, we will be merging Firefox 61 from mozilla-central to beta
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
out Beta 61 to a wider audience with confidence, we'd like to ask that any
risky changes be avoided from April 26th until after the version bump to 62
May 7th.

Some reminders for 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