As a follow-up, the soft freeze is officially in effect until the version bump to 62 takes place on Monday, May 7th. Please use discretion when pushing changes to mozilla-central between now and then.
Thanks, Ryan On Fri, Apr 20, 2018 at 5:43 PM, Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > Just a reminder that this is now less than a week away. Please be mindful > of any large/risky patches targeting 61 as time is running low to land them > before the soft freeze begins. > > Thanks, > Ryan > > On Thu, Apr 12, 2018 at 10:56 AM, Ryan VanderMeulen < > rvandermeu...@mozilla.com> wrote: > >> Hi all, >> >> On April 26th, we will be merging Firefox 61 from mozilla-central to beta >> for >> the first time. 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 61 to a wider audience with confidence, we'd like to ask that any >> risky changes be avoided from April 26th until after the version bump to >> 62 on >> May 7th. >> >> Some reminders for during the soft code freeze: >> Do: >> - Be ready to backout 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 >> > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
