The version bump to 133 has now landed on mozilla-central and the soft
freeze period is over.

Thanks,
Ryan VanderMeulen
Firefox Release Manager

On Tue, Sep 24, 2024 at 8:20 AM Ryan VanderMeulen <[email protected]>
wrote:

> Hello,
>
> With Firefox 131 in the Release Candidate phase this week, we are nearing
> the end of the Nightly 132 cycle.
>
> In order to avoid invalidating the testing we get out of late Nightly and
> to ensure that we can roll out Beta 132 to a wider audience with confidence
> next week, we'd like to ask that any risky changes be avoided from
> Thursday, September 26 until after the version bump to 133 on September 30.
>
> Also, please be advised that string freeze for Firefox 132 begins Friday,
> September 27. In order to ensure that our localizers have adequate time to
> translate strings, please make sure that all string changes have landed by
> EOD Friday.
>
> 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.
>
> Thank you,
> Ryan VanderMeulen
> Firefox Release Manager
>

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAPebk9fMX3c3CX7u2aKGjFf2V8fMicfBQhqG_%2BAC0ChYO2FeRw%40mail.gmail.com.

Reply via email to