-----Original Message----- From: sirbruce@ix.netcom.com [mailto:sirbruce@ix.netcom.com] Sent: Thursday, May 06, 1999 3:48 PM To: toasters@mathworks.com Subject: Re: Ontap P* relase mess.
On 05/06/99 14:56:52 you wrote:
So it looks like I'm going to have to downgrade to 5.2.1P2
from 5.2.2 to
avoid panics from assertions in the netbios name service..
Patches for
5.2.2 are somewhere in the indeterminate future.. (all of
this for bug
12712, which for some reason isn't listed in Bugs Online)
It got moved to REVIEW state today. Should be up on NOW soon.
I agree... many bugs are missing from Bugs Online and the bugs are not updated often enough. Perhaps the people making patch releases don't have full power to update Bugs Online as part of the patch making and bug reporting process.
This brings up one of the points that Tom (?) was ranting on
a week or so
ago.. Why release 5.2.2, a minor bug-patch revision, that don't incorporate patches from its predecessor?
My guess is something like this.
When 5.2.1 was released, naturally 5.2.2 was already being considered and worked on. Shortly thereafter it probably went into testing.
During 5.2.2 testing, some bugs cropped up in 5.2.1. Various patch releases were created to fix some of the problems. However, they did not get as extensive testing as a full "dotdot" release. No doubt someone wanted to roll the P2 patch into 5.2.2, but someone else said it was already too late and doing that would require testing all over again. This was probably unnaceptable for some political reason - anything from something minor like not wanting to slip on the schedule to something major like something in 5.2.2 that some big customer needs and said big customer not being likely to encounter bug 12712.
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. 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.
Perhaps I shoud've called support first, but I just brought
these 760's
online with 5.2.2, under the apparently false impression that I was getting all the up-to-date fixes.. Was there an erratta for
5.2.2 that I
missed that said "THE FOLLOWING IS STILL BROKEN:"?
Would be nice if they had listed known bugs in 5.2.2.
I've burted two RFEs. #14809 RFE - Release notes (Start Here Guide) should list all bugs fixed in a release
#14810 RFE - Release notes (Start Here Guide) should list all bugs fixed in "P" or "D" releases but not fixed in this release
Bruce
-
Norman, Paul