Mozilla plans experimental biweekly Firefox releases prioritizing quality amid industry-wide faster update cadence shifts.
Last week, Brave confirmed that it is adding a new official bypass so that people can keep using popular MV2 addons like uBlock Origin, among others. Like Brave, Firefox, too, has expressed no intention to follow Google, which will soon end all support and completely wipe such extensions.
However, in one regard, Mozilla is considering following Google's lead, as the browser maker is looking to adopt a two-week or bi-weekly release cadence for its browser.
This was confirmed by Sylvestre Ledru, who is the Director at Mozilla, in a new message that informs the Firefox development team about it. However, for now, it is said to be experimental. The message says: "We are planning to move Firefox Desktop and Android from a 4-week release cadence to a 2-week release cadence starting in September 2026. ... This will be an experiment. The goal is to give work that is ready to ship more frequent opportunities to reach users, while making the release process more predictable and reducing pressure on uplifts. .... The current target is to release Firefox 155 on September 1, 2026, instead of September 15."
If you recall, the bi-weekly cadence was first started by Google Chrome earlier this year in March, and this was soon followed by Microsoft as well, which made a similar announcement last month.
Funnily, one of Neowin's readers, rseiler, jokingly quipped that Mozilla would likely follow with a one-week schedule, and it's probably fair to say that they got close to that prediction.
Interestingly, despite Google making the announcement first, it will be the last to actually begin the rollout as it's slated to launch on September 8, whereas Edge will be the first to ship on August 27, just a few days before Firefox does so with version 155.
Despite the quicker schedule, though, Ledru has assured that unfinished development will not be shipped out faster so as to assure quality over speed of delivery. He wrote: " This does not mean that all work needs to ship twice as fast. Work that is not ready should not be rushed, and features can still take the time they need to bake."
Let us know in the comments below on what you think about all browsers moving to this faster update release cycle.
Hope you enjoyed this news post. Feedback welcome.
Posted Tuesday 14 July 2026 at 8:16 am AEST (my time).
News posts: 2023 5,800+ | 2024 5,700+ | 2025 5,700+ | 2026 (to end of June) 2,475
- jenyco2
-
1
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.