Hello, With Firefox 130 in the Release Candidate phase this week, we are nearing the end of the Nightly 131 cycle.
In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 131 to a wider audience with confidence this week, we'd like to ask that any risky changes be avoided from Thursday, August 29 until after the version bump to 132 on August 2. Also, please be advised that string freeze for Firefox 131 begins Friday, August 30. 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: Do: - 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 Do Not: - 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. Thank you, Dianna Smith Firefox Release Manager -- You received this message because you are subscribed to the Google Groups "dev-platform@mozilla.org" group. To unsubscribe from this group and stop receiving emails from it, send an email to dev-platform+unsubscr...@mozilla.org. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CANx%2Bi7aRfZLBfiNhZVUY4m%2BS9RHnFTgAo5oM4imdYfBNdA3i3A%40mail.gmail.com.
