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 -
That more information allow you to make better calls is a truism, no debate. Delaying scheduled events does not seem to be correlated with any of this though If the point is that we might see fewer emergency rollouts as a result, that might surely be.
1 reply 0 retweets 0 likes -
Replying to @paradoxengine @i0n1c
The point is that "you don't need any information, we've made the decision for you, just be a passive consumer" does delay scheduled events. With more complete information, the appropriate schedule can be determined.
1 reply 0 retweets 0 likes -
So we are back to my original question. Do you have a realistic example where a scheduled patching event gets delayed because of this? I just can't see this happening in practice, but I might just lack framing here?
2 replies 0 retweets 0 likes
You're missing the point. You don't consider it an issue unless it's delayed beyond what it would have been without context. We don't agree that is a good bar.
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.