Pascal Chevrel
unread,May 6, 2024, 4:17:49 AMMay 6Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to dev-pl...@mozilla.org, firefox-dev
Hello,
With Firefox 126 in the Release Candidate phase this week, we are nearing the end of the Nightly 127 cycle
In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 127 to a wider audience with confidence next week, we'd like to ask that any risky changes be avoided from Thursday, May 09 until after the version bump to 128 on May 13.
Also, please be advised that string freeze for Firefox 127 begins Friday, May 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:
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.
Thanks,
Pascal Chevrel,
Firefox Release Manager