Yes, that is what they are doing. This all came up when I was told that the longer we "soak" a set of patches in dev, the more likely it is that a different (and untested) set of patches will go...
I feel so much better that the consensus so far agrees with my school of thought. Even though we may not all agree on the "to patch or not to patch" debate, the agreement seems to be that you must...
I am trying to understand how people manage lifecycle patching these days. I am not a sysadmin (I am a DB Architect) and what I am being told is that if there is any lag between patching a dev server...