+dev-platform (correct mailing list this time)

On Tue, May 16, 2017 at 4:15 PM, Ritu Kothari <rkoth...@mozilla.com> wrote:

> Goal: We need to implement a soft code freeze on mozilla-central repo
> during the last week of Nightly cycle.
>
> Nightly version
>
> Soft code freeze
>
> Merge day
>
> 55
>
> June 5th - June 12th
>
> June 12th
>
> 56
>
> July 31st - Aug 7th
>
> Aug 7th
>
> 57
>
> Sept 18th - Sept 25th
>
> Sept 25th
>
> Why?
>
> In the post-dawn world (aka no aurora stabilization), we need a mechanism
> to limit the risk to quality with last-minute changes landing in Nightly
> before Merge day.
>
> How?
>
> The week before Merge day will involve increased scrutiny of patches
> landing in mozilla-central that might regress quality and/or stability.
> This code freeze does not mean mozilla-central repo will be locked and no
> patches will be allowed to land. However, developers are strongly urged not
> to land any fixes that are deemed risky or enable (pref-controlled)
> features a week before Merge day. We recommend you wait until after Merge
> day to land such fixes on mozilla-central.
>
> We will be more aggressive with backing out patches from m-c that cause
> new regressions and merge blockers. If a patch is blamed to introduce a new
> regression/top crasher in Nightly, instead of waiting for a followup fix
> which we normally do, release mgmt team will ask for an immediate backout.
>
> What?
>
> Dos and Don’ts 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 to prioritize fixing merge blockers
>
> Do Not:
>
>    -
>
>    Land a risky patch or a large patch a week before Merge day
>    -
>
>    Land new features a week before Merge day
>    -
>
>    Flip prefs that enable new Features that were untested in Nightly cycle
>    -
>
>    Plan to kick off new experiments
>
> 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

Reply via email to