But why... I don't even fully get why there is a dedicated cycle anyways. Just release an update when there is something worthwhile.
this post was submitted on 13 Jul 2026
52 points (98.1% liked)
Firefox
7351 readers
104 users here now
A community for discussion about Mozilla Firefox.
founded 3 years ago
MODERATORS
This will be OK with me, as long as I don't have this popping up on a regular basis, forcing me to restart my browser:
Fast release cycles might make sense for a new project that is in rapid development.
Fast release cycles for established products make no sense. What I want from a project that is tens of years old is primarily stability. They can do their internal releases at whichever pace they want, but don't push on users updates this frequently, it's just wrong.
Sorry but why is a two week release cycle for a browser necessary?
I don't see why it's necessary for any software. I understand if companies want to release security patches and bugfixes faster. But those releases are usually accompanied by way too many unnecessary changes driven by marketing/product that a lot of people don't give a shit about.
Maybe they should drop the AI and go back to 4.
They already produce nightly builds. Why are people upset that they feel confident to release stables every two weeks?
From 4-week to 2-week:
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.
Definitely going to be vibe coded nonsense at that rate