Chrome Moving To A 4-Week Release Cycle

[phoronix]

Phoronix: Chrome Moving To A 4-Week Release Cycle

Google has been delivering new Chrome milestone releases on a six week cycle for more than one decade while moving ahead they are shifting to a four-week cycle...

http://www.phoronix.com/scan.php?pag...-Week-Releases

[antnythr]

Google probably just doesn't want Firefox to pass them in version number

[Mez']

Version 236 is just around the corner.

[ikeahloe]

Star this issue
If you're tired of chrome/chromium having a uselessly thick border is standard mode (that utilizes CSDs), even though the default themes for KDE, Gnome (+ Ubuntu's Yaru) don't have thick borders, and even thought the windows, macOS, and chrome OS versions don't have an ugly thick border. Give Linux the same level of respect.

[Brisse]

Chrome and Firefox is having a race to the bottom when it comes to release cadence. Every time there's a "major" update, a ton of shitty websites picks it up as if it's "news" and give the browsers the publicity that they crave for. The more often they release, the more publicity. Is this of some benefit to end-users? I doubt it.

[andyprough]

I love it when my spyware and keyloggers are on a tight release schedule. Makes me feel loved.

[fazalmajid]

Moving to an artificially compressed release schedule is precisely why Mac OS X has become a cesspool of buggy releases.

[Teggs]

Maybe Google has and will commit the resources to do this, but it looks to me like a 50% increase in required testing for a benefit that isn't clear. Is there a necessity to release more often?

[ivan.cwb]

Next week:
"Mozilla Moving to A 3-Week Release Cycle..."

[carewolf]

So it wasn't buggy enough yet?