Hi all, we're fast approaching the start of the 72 beta cycle on December 2nd, with our "Feature complete" milestone for 72 tomorrow, November 22nd.
In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 72 to a wider audience with confidence, we'd like to ask that any risky changes be avoided from November 25 until after the version bump to 73 on December 2nd. 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 and the Release Management team _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
