Oh shit, more stuff to fix in user.js.
Jebus. They think instability is a virtue.
They've been itching for more releases to push more AI updates for a while. I wish I was exaggerating. Here's three examples of AI features being tacked onto bugfix releases:
(For those who don't know, bugfix releases only change the final part of the version number and are meant to fix bugs, while feature updates are meant for larger releases and tend to introduce them.)
That's not necessarily the case. There's plenty of evidence that continuous delivery can lead to better software.
I agree in some respects. If you have something like Gnome with 6 month development cycles, you are kinda encouraged to push features even if they are not ready, otherwise you have to wait 6 months to try again. And as we've seen with stuff like triple buffering, it was painful. It was almost ready, missed the cycle, then other Gnome changes were made, then it had to be rebased, then go back to step 1.
With a shorter cycle, missing a cycle isn't as big of a deal and in theory you can polish it more without it being the end of the world.
But Firefox already had a monthly release cycle. I don't see how going from a monthly to fortnightly is really that different.
A place to discuss the news and latest developments on the open-source browser Firefox.
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.