Hi,
With Firefox 100 in Release Candidate phase this week, we are
nearing the end of the Nightly 101 cycle.
In order to avoid invalidating the testing we get out of late
Nightly and to ensure that we can roll out Beta 101 to a wider
audience with confidence this week, we'd like to ask that any
risky changes be avoided from Thursday, April 28 until after the
version bump to 101 on May 2.
Also, please be advised that string freeze for Firefox 101 begins
Friday, April 29. 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
-- Pascal Chevrel Firefox Release Manager + Firefox Nightly & Beta community management
--
You received this message because you are subscribed to the Google Groups "firef...@mozilla.org" group.
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/64c7bd6a-cc6d-a247-7401-1a8b0162388e%40mozilla.com.