With Firefox 77 RC shipping soon, we are nearing the end of the Nightly 78 cycle.
In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 78 to a wider audience with confidence next week, we'd like to ask that any risky changes be avoided from Thursday May 28 until after the version bump to 79 on June 1st. This also means that by mid-week, feature work targeting 78 should be complete and ready to ride the trains. 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, Julien & the Release Management team _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
