On 05/06/99 20:35:58 you wrote:
I'm not surprised to see Bruce has pretty much got the scenario of how this happened since he's an ex-NetAppian. In fact 5.2.2 was in test as other bugs came in.
Hey, the process can always change. :) I was mostly just guessing given the circumstances, and knowing that Netapp wouldn't not include the patch without a reason.
Since the CIFS problem, 12363, was biting a number of customers and it caused a Panic, we wanted to get 5.2.2 into manufacturing as fast as possible. Judgement call on our part, we decided not to restart all the testing and just go with 5.2.2 as it was in order to have a new GA release that manufacturing would ship.
I was trying to think of possible ways around this and couldn't really think of a good one. One idea, though, would be to make sure that any P releases from a previous version that aren't rolled in have P releases made for the new version by the time it's released. That way customers on 5.2.1P2 can get 5.2.2P2 if they have a specific bug, while 5.2.1 customers can pick the regular 5.2.2. You could put something on NOW basically saying that they shouldn't download 5.2.2P2 unless they were experiencing that particular bug, because it hadn't been thoroughly tested.
Bruce