Firefox Are Moving to a Two‑Week Release Cycle Starting September

3 months ago by Hal-5700X to c/firefox

MantisToboggon 22 points 3 months ago

Maybe they should drop the AI and go back to 4.

path: 0 24755529, hotness: undefined, score: 22, children: 0
lnxtx 17 points 3 months ago

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.

path: 0 24754745, hotness: undefined, score: 17, children: 1
Matty_r 13 points 3 months ago

Definitely going to be vibe coded nonsense at that rate

path: 0 24754745 24757294, hotness: undefined, score: 13, children: 0
webkitten 14 points 3 months ago
path: 0 24760136, hotness: undefined, score: 14, children: 1
dotned 9 points 3 months ago

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.

path: 0 24760136 24760689, hotness: undefined, score: 9, children: 0
JigglySackles 13 points 3 months ago

But why... I don't even fully get why there is a dedicated cycle anyways. Just release an update when there is something worthwhile.

path: 0 24762268, hotness: undefined, score: 13, children: 0
mannycalavera 5 points 3 months ago

They already produce nightly builds. Why are people upset that they feel confident to release stables every two weeks?

path: 0 24758160, hotness: undefined, score: 5, children: 0
calcopiritus 4 points 3 months ago

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.

path: 0 24763862, hotness: undefined, score: 4, children: 0
perishthethought 2 points 3 months ago

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:

image

path: 0 24765506, hotness: undefined, score: 2, children: 0
BeigeAgenda -8 points 3 months ago

FF is always updating already, yet another reason to switch.

path: 0 24757021, hotness: undefined, score: -8, children: 3
Carighan 5 points 3 months ago

You mean from your 4-weeks-cycle browser to any other one, which are all (through being based on Chrome) on 2-weeks-cycles? Or they're intentionally lagging behind their upstream, which is the exact same only with less control as you simply choosing not to update your FF if an update is available?

path: 0 24757021 24759356, hotness: undefined, score: 5, children: 2
BeigeAgenda 5 points 3 months ago

Good point, It may not be my smartest comment.

Sometimes I just get tired of all the updates happening all the time from everywhere, and that each update often means changes that makes the program worse.

path: 0 24757021 24759356 24760613, hotness: undefined, score: 5, children: 1
ramasses 4 points 3 months ago
Stay calm and sudo pacman -Syu
path: 0 24757021 24759356 24760613 24764481, hotness: undefined, score: 4, children: 0
firefox
firefox

@lemmy.world

login for more options
7592
590
845

A community for discussion about Mozilla Firefox.

go to feed...