• SauceFlexr@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    4 months ago

    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.

    • 0x0@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 months ago

      I read somewhere (commentes in that video) that CS ignored their own customer-configured stagger upgrades for some upgrades…

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        4
        ·
        4 months ago

        Apparently those settings are only for updates to the software itself, not for updates to the definition files.

    • NateSwift@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      9
      ·
      4 months ago

      I heard somewhere that the updated ignored staging settings set. So even if companies had it set to only roll out to a subset of their computers it went everywhere

      • SauceFlexr@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        4 months ago

        Oof. Then that seems more on the ops side of things. Interesting. I can’t wait for them to never share what happened so we can all continue to speculate. 😂