Mozilla Shifting Firefox To A Four-Week Release Cycle

[phoronix]

Phoronix: Mozilla Shifting Firefox To A Four-Week Release Cycle

Mozilla announced today they are tightening up the Firefox release cycle even more... Expect to see new Firefox releases monthly...

http://www.phoronix.com/scan.php?page=news_item&px=Firefox-Four-Week-Release-Cycle

[AsuMagic]

Thank god, we were starting to lag behind Chrome's version numbers. Suck it, Google!

[uid313]

Firefox just got dark theme support, really nice.
Hope to see it get refined to include to auto-switch in the devtools too, and in about:debugging, about:home, and about:blank and other places too, now its just in aboutreferences and in some other places.
It also recently got event debugging which seems really nice.

[yoshi314]

i wonder how disruptive that may be to people developing major features that take significantly longer to land.

i know how development workflow works, just wondering how you can get a major rework of a browser into shippable state with shorter and shorter release cycles.

[tildearrow]

They shouldn't do major releases that often. I don't truly agree with the "release early, release often" model.
It gives developers less time to do quality assurance, and hence may yield more bugs.

People who want this model can just use the Developer Edition.

[DanL]

I don't truly agree with the "release early, release often" model.
It gives developers less time to do quality assurance, and hence may yield more bugs.

Yeah, it seems like Mozilla wants more lab rats.

[tildearrow]

Yeah, it seems like Mozilla wants more lab rats.

*inefficient lab rats (Average Joe doesn't know how to make good bug reports)

Do they even read the automatic crash reports?

[Ray_o]

i wonder how disruptive that may be to people developing major features that take significantly longer to land.

i know how development workflow works, just wondering how you can get a major rework of a browser into shippable state with shorter and shorter release cycles.

They normally don't enable them by default and if you want to enable them you go to "about:config" page.

[TheCycoONE]

i wonder how disruptive that may be to people developing major features that take significantly longer to land.

i know how development workflow works, just wondering how you can get a major rework of a browser into shippable state with shorter and shorter release cycles.

You do your major rework on a different branch until it's production ready, dependent features don't land until the 'rework' lands, and anything that does land in the middle releases gets merged forward into the rework. I don't see how it's that different than the major rework they're doing now that takes several versions to land (all the quantum stuff)

[birdie]

This is madness.