«  Firefox 111  »
Go to Release channel

Release DateMarch 14, 2023
Release OwnerDonal Meehan
Nightly cycle length4 weeks
Beta cycle length4 weeks
Corresponding ESR release 102.9.0
Milestones
Nightly starts

The first day of the cycle is Merge Day. After merging mozilla-central to mozilla-beta, we bump the Nightly version number on mozilla-central and a new development cycle starts for Firefox. A new Firefox Nightly is shipped every 12 hours.

January 16
Soft Code Freeze starts Draft beta release notes

We are nearing the end of the Nightly cycle. Don't land new untested features. Risky changes should be avoided after 8:00 AM UTC until after the nightly version bump on Merge Day.

February 9
String Freeze starts

In order to ensure that our localizers have adequate time to translate strings, please make sure that all string changes have landed by end of day.

February 10
Merge day

This is the day in the release cycle when we merge mozilla-central into mozilla-beta. This is the end of the development cycle for Firefox 111 and the beginning of our Beta stabilization cycle.

February 13
Beta 1 Go to build

Built manually just after the merge. It is rolled out to 25% of our beta population. Some experimental features are still activated to watch their behavior on a wider population. These experimental features will be deactivated mid-cycle. Uplift requests are open.

February 13
Beta 2 Go to build

First automated beta of the cycle. It is rolled out to 50% of our beta population. Build starts at 21:00 UTC.
Stabilization work via uplifts.

February 14
Beta 3 Go to build

Beta rollout bumped to 100% provided stability is good. Build starts at 21:00 UTC. Stabilization work via uplifts.

February 16
Support content creation

User affecting changes were identified and provided to the support.mozilla.org team. The support content for this release can now be created and will be translated before RC week.

February 17
Beta 4 Go to build

Build starts at 21:00 UTC. Stabilization work via uplifts.

February 19
Beta 5 Go to build

Build starts at 21:00 UTC. Stabilization work via uplifts.

February 21
Beta 6 Go to build Last early beta

On a regular 4 weeks beta cycle, Beta 6 is the last beta with experimental features still activated. Build starts at 21:00 UTC. Stabilization work via uplifts.

February 23
Beta 7 Go to build

Experimental features are no longer activated at compile time. Build starts at 21:00 UTC. Stabilization work via uplifts.

February 26
Support content localization

New content on support.mozilla.org team is finalized, uploaded to the server and provided to our localization teams internationally.

February 27
Beta 8 Go to build

Last week of the beta cycle. Build starts at 21:00 UTC. Stabilization work via uplifts.

February 28
Beta 9 Go to build Last beta uplifts

On a regular 4 weeks beta cycle, this is the last beta and thus the end of beta uplifts. Build starts at 21:00 UTC.

March 2
Release Candidate Go to build

We merge our mozilla-beta repository to mozilla-release and close mozilla-beta until the next merge day. We then build our Release Candidate from mozilla-release. This is the build we intend to ship a week later unless we need to build a second Release Candidate to fix a major quality or business critical issue.

March 6
Release Candidate Release notes finalized

Our Release Candidate is shipped to all of our beta population.

March 7
Release day!

We ship Firefox 111 at 14:00 UTC (6AM PST) at 25% rollout.

March 14
Planned dot release

Two weeks after the release, we ship a dot release to address identified quality issues if needed. We may have to ship other dot releases before that date. If this is the case and post-release quality issues are already fixed and shipped, the decision on shipping or not the planned dot release is on the release management team.

Please note: pwn2own 2023 takes place on March 22-24. If there are any Firefox exploits announced, then we may need to chemspill prior to the planned dot release. The timing of the chemspill may impact the planned dot release. We will send further communication closer to the planned dot release date.

March 28