Hi everyone, anything that lands on integration trees (inbound or autoland) from now on will be after the cutoff for 71, so consider the soft freeze lifted.
Thanks, Julien On Mon, Oct 14, 2019 at 1:02 PM Pascal Chevrel <pchev...@mozilla.com> wrote: > Hi all, > > We will be merging Firefox 71 from mozilla-central to beta for the first > time later today, Oct. 14. > > In order to avoid invalidating the testing we get out of late Nightly > and the early Developer Edition builds and to ensure that we can roll > out Beta 71 to a wider audience with confidence, we'd like to ask that > any risky changes be avoided from Oct. 14 until after the version bump > to 72 on Oct 21. > > 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 affects 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 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, > > Release Management Team > > -- > Pascal Chevrel > Firefox Release Manager > + Firefox Nightly community management > > _______________________________________________ > dev-platform mailing list > email@example.com > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list firstname.lastname@example.org https://lists.mozilla.org/listinfo/dev-platform