this post was submitted on 21 Jul 2024
29 points (96.8% liked)
Technology
59298 readers
6261 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That answered a lot of questions.
I hope they publicly state how they pushed a bad file, but I doubt it.
Seems like someone really didn't pay attention to what they were doing, and they might have an internal problem with QA.
They don't have a lack of quality assurance. They have a lack-of-quality assurance.
Their QA worked better than intended, they had tests fail worldwide and tons of results to work off of hahaha
As someone that works in QA, yeah, they needed something to catch this. I saw someone mention somewhere without a source that they missed it as all test machines have their full suite of software installed. In that scenario, the computer wasn’t affected. So for QA it seems their labs might need to be more in tune with the user base.
However, the fact that they are able to push this so quickly worldwide seems like a big process issue. I get 0 day issues and that is how they justify it. But deploy to a small subset of customers before going global seems more reasonable.
I read somewhere (commentes in that video) that CS ignored their own customer-configured stagger upgrades for some upgrades...
Apparently those settings are only for updates to the software itself, not for updates to the definition files.