With Firefox 111 in the Release Candidate phase this week, we are nearing the end of the Nightly 112 cycle.
In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 112 to a wider audience with confidence this week, we'd like to ask that any risky changes be avoided from Thursday, March 9 until after the version bump to 113 on March 13.
Also, please be advised that string freeze for Firefox 112 begins Friday, March 10. 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.
Dianna SmithFirefox Release Manager
You received this message because you are subscribed to the Google Groups "firef...@mozilla.org
To unsubscribe from this group and stop receiving emails from it, send an email to firefox-dev...@mozilla.org
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/firefox-dev/CANx%2Bi7bbsAJ3GQPGxS3EkyRVt-H9QZLC5K9pdfOno%3DLGwoZKjA%40mail.gmail.com