Chrome Moving To A 4-Week Release Cycle

[Mez']

What we see here is the drawback of Agile and Scrum specifically. For what release frequency is Agile/Scrum still relevant?
How much is too much? They can develop on a sprint schedule, but they don't have to release after every sprint...
It's getting to a point where it's becoming a stereotype of itself. Every new half feature is good enough for pushing a release.

That's why I'll always prefer Lean over Agile.

[Mez']

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

Let's be honest, you just like it tight.

[carewolf]

So it wasn't buggy enough yet?

[ivan.cwb]

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

[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?

[fazalmajid]

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

[andyprough]

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

[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.

[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.

[Mez']

Version 236 is just around the corner.