On 04/26/99 17:11:16 you wrote:
So who tested cluster takeover/giveback during the "comprehensive development and release procedure"...? Can they tell me what I'm doing wrong? Was bug 14194 (Filer crashes during boot during partner giveback) discovered during this testing and 5.3 was released anyway? If so, I think you guys are carrying that MS partnership a bit too far...
Ok, maybe comparing you guys to MS was below the belt. I'll take that back. But I'm still curious how 5.3 made it as far as it did? I thought clustering was the hot new thing at NetApp.
Did somebody decide a boot during giveback was ok for now? It's not a problem until the partner s fixed or until your testing to see that you got what you paid for. If this was the case, a "known bugs list" would've been nice.
I believe Netapp has said before publically that they do find bugs during testing that they don't fix by release time. This is not to say that they don't fix any, but that little bugs or big bugs that only appear under relatively rare circumstances won't be addressed until a later release.
I've suggested before that Netapp publically reveal bugs that have only been discovered internally at Netapp, but I think their current policy is only to reveal bugs online that customers have encountered themselves.
So it is possible they discovered the bug in advance and didn't think anyone (or perhaps very few) would encounter it. Or perhaps they didn't. They do have pretty big testing procedures for new software releases but I don't think they regression test every possible scenario.
Bruce
On Mon, 26 Apr 1999 sirbruce@ix.netcom.com wrote:
I've suggested before that Netapp publically reveal bugs that have only been discovered internally at Netapp, but I think their current policy is only to reveal bugs online that customers have encountered themselves.
I personally would like to see a list of bugs fixed in major releases, just as the list that appears when you try to d/l 5.2.1P2. Granted that I would like to install 5.3 to take advantage of the new features, but how can I be sure that all bugs fixed in 5.2.1P2 are also fixed in 5.3 unless all of them are individually listed. At least a statement as to the code base used for a major release should be provided prior to the download, i.e. release 5.3 is based on patch release 5.2.1P1 plus fixes from the following bugs ...
Tom