home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.security.misc:2379 comp.org.eff.talk:8147
- Newsgroups: comp.security.misc,comp.org.eff.talk
- Path: sparky!uunet!usc!cs.utexas.edu!sun-barr!ames!agate!dog.ee.lbl.gov!hellgate.utah.edu!csn!teal!bhayden
- From: bhayden@teal.csn.org (Bruce Hayden)
- Subject: Re: Stupid Licenses (YUCK!)
- Message-ID: <bhayden.725651090@teal>
- Sender: news@csn.org (news)
- Nntp-Posting-Host: teal.csn.org
- Organization: Colorado SuperNet, Inc.
- References: <bhayden.724690634@teal> <1992Dec19.023609.26000@news2.cis.umn.edu> <1992Dec22.034142.14471@fsl.noaa.gov> <1992Dec28.002314.21233@news2.cis.umn.edu> <1992Dec29.002945.4377@qiclab.scn.rain.com>
- Date: Tue, 29 Dec 1992 17:44:50 GMT
- Lines: 20
-
- leonard@qiclab.scn.rain.com (Leonard Erickson) writes:
-
- >>> Would you postpone a release with known bugs (documented in a 'here there
- >>> be dragons' addendum) which would replace a previous, more buggy version?
-
- >>Why can't they just provide a release that fixes the old bugs without
- >>introducing (known) new ones? Featurality first is the only explanation.
-
- >Well, I know of a case where this was tried, but one of the fixes involved
- >switching from a no longer supported (and *buggy*) comm library to a new
- >library that turned out to be buggier than expected. While waiting for
- >the fixes, the programmers decided to add a few of the "easy" features
- >users had been requesting. Which (of course) lead to a few new bugs.
-
- Appears to me to be a management problem, not a technical problem.
-
- Bruce E. Hayden
- (303) 758-8400
- bhayden@csn.org
-
-