With Firefox 90 entering the Release Candidate phase this week, we are nearing the end of the Nightly 91 cycle.
order to avoid invalidating the testing we get out of late Nightly and
to ensure that we can roll out Beta 91 to a wider audience with
confidence next week, we'd like to ask that any risky changes be avoided
from Thursday, July 8 until after the version bump to 92 on July 12.
please be advised that string freeze for Firefox 91 begins Friday, July 9. In order to ensure that our localizers have adequate time to
translate strings, please make sure that all string changes have landed
by EOD Friday.
Some reminders for the soft code freeze period:
- Be ready to back out 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
- Land a risky patch or a large patch
Land new features (that affect 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 the Nightly cycle
- Plan to kick off new experiments that might impact a feature's merge readiness
Please let us know if you have any questions/concerns.