CompuServe Thread

#R11c2 BUG VERIFY HELP

4 messages in this thread
#21588From: Duff Kurland [Adesk]Nov 23, 1991 4:41 AM
[Continued] …There *always* ONE MORE BUG… ..and as long as you're doing an update, you might as well fix that one, too… and why not update to the latest version of the PharLap extender, and slip in that new Sooper Dooper XSVGA driver while we're at it… and maybe an AME update… and Zortech C++ ADS support… but the bug fixes cause more bugs elsewhere, and the updated DOS extender doesn't work on such-and-such machine in the QA lab… and before you know it, you've spent months and months of effort for very little gain, while slowing down the development of new functionaility also demanded by present and prospective customers. No. We'll do our best to test the product thoroughly prior to initial shipment, and plan to accommodate perhaps one bugfix update after it's been put through the wringer by real users for a month or two (and if they've encountered any serious problems)… but then get on with development of the next release so we can get that out, with all known bugs from the previous release fixed, in a timely manner.
#21592From: Mark W. Burns – TKLP IncNov 23, 1991 8:53 AM
Duff, I figgured that if I pushed hard enough I'd finally get SOMEBODY from Adesk to respond in a definitive manner…<g> Thanks for the response. Yes, we are *VERY* aware of a large number of bugs with the AES DXF translator. Because of all those bugs we chose not to purchase it! (we had it on loan for trial for about 2 weeks, and we needed a great deal of technical help from our AES Dealer's technical guru to get ANY files translated successfully at all!) One of the problems we encountered in that testing was that ACAD (DOS) produced a DXF file with uppercase symbol names & such, and the AES software didn't take too kindly to this (again – this is THEIR bug, not ACAD's). However, what I sort-of recall now is that this fellow was running some AWK programs to massage the DXF files comming out of AES into condition, and one of the things I think he did was to convert the whole file into uppercase…which seemed to work ok at first…until AUDIT heaved up big time all over it. OK, consider my campaign for R11c3 dropped as of now. Consider my campaign to speed up R12's release started now!<grin> Look Duff, I don't want much…just *EVERYTHING* and I want it *NOW*! <Big Grin> I see your prespective a bit more clearly now about infinite bug-fix versions, and <*sigh*> OK, you're right. I suppose it takes a *SERIOUS* bug (like say the LINE command going *thud* in certain situations) that's likely to be encountered by *lots* of folks to warrant such an effort, and then you're likely to want to do as little "fixing" as you can get away with. Does that synopsis sound about right? Again, thanks for the explanation of the process. Mark Burns – TKLP Inc.
#21660From: Duff Kurland [Adesk]Nov 23, 1991 6:52 PM
Mark – Yup, that sounds about right.
#21694From: Mark W. Burns – TKLP IncNov 23, 1991 11:40 PM
Duff, Rats. I was hoping I'd gotten it wrong…<grin> Oh well…at least you folks know about the problem for R12 now… and If need be I can edit the faulty DXF files into acceptable shape (PITA that that'll be), so I guess I can live with this…but BOY was it ever a PITA to nail down tho! Regards, Mark Burns – TKLP Inc.