Article View: comp.sys.mac.oop.macapp3
Article #216Re3: Takeover - QA
From: Research SW Design, D Goldman,PR...
Date: Mon, 04 Jan 1993 21:38
Date: Mon, 04 Jan 1993 21:38
16 lines
1087 bytes
1087 bytes
Bob -- Your point is well-taken, but the important issue to me is that this is NOT an error with the patch. If my application currently works fine because it unwittingly takes advantage of a bug in MacApp, then a new release of MacApp in which that bug is fixed _must_ be allowed to crash my application. If I can't stand to face such possibilities, then I should never load _any_ update of MacApp onto my system. This is just like Jesse's scenario in which a code segment now exceeds 32K. Neither one of these problems is MacApp's responsibility, and neither one of these problems would be prevented by a _thousand_ person-weeks of QA testing within a hermetically sealed Apple QA laboratory. -- Dave
Technical Details
Message-ID:
<726183995.5145919@AppleLink.Apple.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!wupost!spool.mu.edu!olivea!apple!applelink.apple.comShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!spool.mu.edu!olivea!apple!applelink.apple.com From: RSD@AppleLink.Apple.COM (Research SW Design, D Goldman,PRT) Newsgroups: comp.sys.mac.oop.macapp3 Subject: Re3: Takeover - QA Message-ID: <726183995.5145919@AppleLink.Apple.COM> Date: 4 Jan 93 21:38:00 GMT Sender: daemon@Apple.COM Organization: AppleLink Gateway Lines: 16