Oh, that's true.
Gosh, they're doing automatic roll-outs without a proper pipeline. That is scary.
On the other hand, customers have been rewarding this sort of reckless behavior. We can see that on here.
Discussion
Yeah, fair share of people here advocating for aggressively fast updates "even if it breaks shit". There's always a balance.
That's one reason I trust Nostrudel. They offer a cutting-edge version "next.nostrudel.ninja" where they also don't activate new versions until you press the button. A couple of times, it broke something, so I just went and used the normal one, again.
Beta test environment, basically.
We used to do this at work. A public staging environment.
It think this sort of parallel release alleviates a lot of the curiosity the users feel (they want to "see" the new thing and try it out), while mitigating risk.
Even if you have a desktop or mobile app, you can created a simulated/test environment to show off a new feature and get feedback from users. There are Android emulators and stuff.
IMO frequent for security, and heavy testing regime and approval signoff pipeline
for everything else, make it optional, at all
The problem is not that there fast increments, it's that the increments are often barely tested, unreleased, and bug-fixes are rolled in with new features. So, you're basically forced to install every update, immediately, because what they delivered the last time is broken and this new one contains the fix. But the new one is also broken.
Software Version Mafia 😂
And everything straight to full-rollout to production. Boom. And then everyone installs it and it immediately crashes. That's not even an alpha version, it's just a prototype.
And then it's like,
Ummm... my bad, reinstall the previous one.
yeah, move fast and break things should not be the motto of the QA lol, QA should be pig headed salty bastards who are sticklers for an extensive test routine to be run and passed, and i mean, like, a giant long checklist of features that should work that have to be run through a standard regime
and not even touch it without the unit tests all 100%, fix the damn tests, and no damn disabling the damn tests damn you
We call those people "beta testers," and their enthusiasm should be channeled to help produce a stable product for the average user.
EXACTLY!!
I'm a natural for the beta tester role, as are many of the power users, and we tend to be mentally prepared for the software to mess our stuff up or act wonky.
Roll out to us _first_ and then roll out to everyone else a couple of days or a week, later.
And make the updates opt-in. Sure, it's better for security to stay fully up-to-date, but if someone wants to never update their desktop, it's on him if he gets hacked.
In commercial systems, the sysadmins should be responsible for validating and determining the necessity of updates.