Well, Google prioritises releasing patches from qualification based on available public information, so there's one example 
-
-
:+) it still is about prioritising though, not active deprioritization of something that would have otherwise occurred - which is what, maybe erroneously, I've read in Stefan's tweet.
1 reply 0 retweets 0 likes -
Replying to @paradoxengine @i0n1c
Ah, we're well staffed and the difference between prioritized and not is small, but I think we're the exception. I've heard gov change management horror stories, for example.
1 reply 0 retweets 0 likes -
I won't argue with that :) I am still somewhat unconvinced that somewhere a sysadmin is going to say "know what, this patch here that would be part of my forced uodate schedule, don't know enough about this one bug it fixes, will wait another month to install it"
1 reply 0 retweets 1 like -
Replying to @paradoxengine @i0n1c
I think it's more "standard qualification takes 3 months, see no reason to put my neck on the line and let this one jump the queue, that's a lot of paperwork"
1 reply 0 retweets 1 like -
So maybe reformulating, the claim is not that things will go slower, but that some exceptional things won't go faster? That's a substantially different, less boisterous one, that I can grok better but also seems less impactful?
1 reply 0 retweets 0 likes -
Replying to @paradoxengine @i0n1c
No, the problem is patching is disruptive. Knowing why you're being disrupted and being able to understand and reason about the risks allows you to make better decisions.
2 replies 0 retweets 4 likes -
However saying "people won't scramble" is very different than saying "people will wait"?
1 reply 0 retweets 0 likes -
Replying to @paradoxengine @i0n1c
People are waiting already, unless they're going to wait even more, you don't consider it a problem?
1 reply 0 retweets 0 likes -
No, I just don't think it's fair to say that folks will be waiting (more) *as a result of this change*. That the status of patching is an unmitigated disaster I fully agree on, hence my "for the sake of the argument" at the beginning
1 reply 0 retweets 0 likes
The only difference with this changes is less information. Therefore, patches that would have been prioritized with context will not be. In my opinion, that is waiting more.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.