I consider this OK to deploy. It does introduce a new OOPS (bug #726985), but in a case somewhat rarer than the one it fixed. It should be a net win on the OOPS count front, and the new OOPS does not constitute service degradation.
I consider this OK to deploy. It does introduce a new OOPS (bug #726985), but in a case somewhat rarer than the one it fixed. It should be a net win on the OOPS count front, and the new OOPS does not constitute service degradation.