Post

Una Kravets
@una.im

I don’t think this will make a huge difference for feature timelines, but it will improve bug fix landings and just make the browser more nimble

Una Kravets
@una.im

That wasn't the case when you had something like a CSS rename or behavior change since it wasn't a security issue. If you miss a branch cut for a new feature by one day you don't have to wait an entire month now to land it.

Una Kravets
@una.im

I’m sure there was! I don’t personally know what the official reasoning to formally institute this change was, but as someone who’s often waiting for features to go from beta to stable because of the release cue, I welcome it :)

Una Kravets
@una.im

I think it’s also great to just be able to iterate faster. We often will release small incremental changes and features that may rely on one another.

Rick Byers
@rbyers.net

Personally I believe this will help us to increase quality and stability. Today there's a lot of merging changes to release branches because they can't afford to wait, which creates some instability. With 2-week releases I expect more can just "ride the train".

claas
@claas.dev

So the top right “Update” button you see when someone screen shares will become even more frequent 😆

Rick Byers
@rbyers.net

Shouldn't be, we were already doing weekly security pushes. Half of those updates will now just get more than just security fixes.

Banda Bassotti
@orpach.neocities.org

Interesting. They're going to overtake firefox on version numbers again, it's been a while. RIP anyone using a formula to set their webscraper's user agent string though.