This is a staging environment for whattrainisitnow.com

«  Firefox 134  »
Go to Release channel

Release DateJanuary 7, 2025
Release OwnerPascal Chevrel
Corresponding ESR releases 128.6.0 · 115.19.0?
Latest BuildID 20241122214930
Nightly cycle length4 weeks
Beta cycle length6 weeks
Release notes Nightly notes
Milestones
Desktop, Android & iOS
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.

 October 28
3.5 weeks ago
Deadline to request accessibility engineering review

Accessibility engineering review has been requested (using the a11y-review flag on Bugzilla) for new (or significantly redesigned) UI that requires assessment to determine whether it is accessible to people with disabilities.

 November 1
3 weeks ago
Deadline to request manual QA

QA has been informed (via a Jira ticket) about features that require manual testing during the nightly and/or beta cycle.
Feature technical documentation is also required to draft Test Plans and Test Cases.

 November 1
3 weeks ago
Build ready for QA in nightly

Features with a QA request are ready for testing to assess feature quality and provide a formal test report by the end of Week 3 of the nightly cycle.

 November 8
2 weeks ago
Build ready for QA in beta

If nightly testing was skipped then features should be in a testable state by this date for beta testing.

 November 21
2 days ago
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.

 November 21
2 days ago
QA Test Plan approval due

For features requiring Nightly testing, the QA team appreciates an earlier sign-off from the project teams. If an early sign-off is not available or testing is required only in Beta, the approval milestone will be the final deadline for any feature Test Plan sign-offs. No feedback/sign-off on QAs Feature Test Plan could result in misalignment on testing scope, incomplete test coverage and invalid bugs.

 November 22
Yesterday
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.

 November 22
Yesterday
QA pre-merge regression testing done

QA assess build readiness for shipping to Beta by running a set of Regression test cases and shares a test report. Nightly Regression coverage is limited compared to Beta Regression testing throughout the Beta cycle.

 November 22
Yesterday
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 134 and the beginning of our Beta stabilization cycle.

 November 25
No working day before milestone
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.

 November 25
No working day before milestone
Beta 2 Go to build

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

 November 27
In 2 working days
Beta 3 Go to build

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

 November 29
In 4 working days
SUMO 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.

 November 29
In 4 working days
Beta 4 Go to build

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

 December 2
In 5 working days
Beta 5 Go to build

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

 December 4
In 7 working days
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 13:00 UTC. Stabilization work via uplifts.

 December 6
In 9 working days
Beta 7 Go to build

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

 December 9
In 2 weeks
SUMO content localization

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

 December 9
In 2 weeks
Beta 8 Go to build

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

 December 11
In 2 weeks
Pre-release QA sign-off

A week before the final sign-off, QA shares preliminary test reports for each feature riding the train. This pre-release sign-off can be Green, Yellow or Red.

 December 11
In 2 weeks
Beta 9 Go to build Last beta uplifts (sec-approval request deadline)

On a regular 4 weeks beta cycle, this is the last beta and thus the end of beta uplifts, including security bugs for this release (sec-approval+ on Bugzilla). Build starts at 13:00 UTC.

 December 13
In 2.5 weeks
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.

 December 16
In 3 weeks
Release Candidate Release notes finalized

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

 December 17
In 3 weeks
Release day!

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

 January 7
In 6 weeks
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.

 January 21
In 8 weeks