We know from discussions with tipsters (and from the simple fact that rumored phones take a century to get released) that Verizon tests the crap out of things -- generally speaking, anyway. Apparently that wasn't the case with the latest Tour
firmware to see action, though, because 188.8.131.52 got pulled within a few hours of its release -- but not before wreaking havoc with at least a few users' phones, some to the point where Verizon went ahead and recommended a replacement unit. When you consider that BlackBerrys are probably among the most mission-critical devices in any carrier's lineup, this is a big deal; Verizon did the right thing by moving swiftly to pull the bunk build, but the question remains: how did such a quickly-detected problem make it through what was very likely an exhaustive internal testing phase?
*Verizon is currently in the process of acquiring AOL, Engadget's parent company. However, Engadget maintains full editorial control, and Verizon will have to pry it from our cold, dead hands.