Comment 37 for bug 642839

I agree. My point was that this isn't a usual bug where someone finds a
problem and then resources need to be brought onto the problem to identify and
resolve it. This is a case where the usual processes were bypassed to do
something that at best hadn't been fully considered.

I do wonder, given that the suggested resolution came from a member of the
release team, if this entire mess might have been avoided if the existing
processes for post feature freeze design changes had been followed.