Xref: utzoo news.software.b:2214 comp.sources.d:3619
Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!cwjcc!ukma!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: news.software.b,comp.sources.d
Subject: Re: When is C News being released?
Message-ID: <918@twwells.uucp>
Date: 11 May 89 16:26:19 GMT
References: <24133@agate.BERKELEY.EDU> <1989May9.191034.3424@utzoo.uucp>
Reply-To: bill@twwells.UUCP (T. William Wells)
Followup-To: comp.sources.d
Organization: None, Ft. Lauderdale
Lines: 26
Summary:
Expires:
Sender:
Distribution:
Keywords:

Followups have been directed to comp.sources.d.

In article <1989May9.191034.3424@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
: Personally, I do not consider a steady stream of revised releases to be
: a good sign... :-)

Hooray!

I've become really disgusted with the amount of patching that goes
into some of the posted software. I would much rather wait for a
tested release than be the unintentional beta tester that many people
have become.

E.g., I would have brought up elm to replace mailx but there was
patch 1, patch 2, ..., patch 7! All in the space of a few weeks. It
might have been the case that elm would have worked fine for me but
this was *not* encouraging!

Please folks, if you have to release something that you don't *know*
is reasonably tested, note it as a beta. And tell us what *has* been
tested.

Please?

---
Bill                            { uunet | novavax } !twwells!bill