From: Larry McVoy <lm@mcvoy.com>
To: Steve Jenkin <sjenkin@canb.auug.org.au>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Has this been discussed on-list? How Unix changed Software.
Date: Wed, 7 Sep 2022 15:36:05 -0700 [thread overview]
Message-ID: <20220907223605.GS31856@mcvoy.com> (raw)
In-Reply-To: <8DDF5A51-AABF-41AF-993C-4D087903BDC9@canb.auug.org.au>
On Thu, Sep 08, 2022 at 07:27:26AM +1000, Steve Jenkin wrote:
> Would your folk ship code with a list of outstanding bug reports?
Absolutely, there were always open bug reports that couldn't be
reproduced, or were a side effect of misusing the product, etc.
We didn't ship with stuff that we thought should be fixed and could
be fixed.
> I don???t think Ken & Dennis did that.
I wasn't there but it's hard to imagine anything as complex as an
operating system went out the door with everything fixed. I dunno
how the kernel was done back in the day, but for us, doing a release
was a 6 month process. If you reset that process each time a new
bug comes in, you'll never ship. At some point, you have to balance
the set of features and bugfixes you can fix against whatever new
thing that shows up. It's definitely an art to get that right.
next prev parent reply other threads:[~2022-09-07 22:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 15:07 Douglas McIlroy
2022-09-06 17:13 ` Larry McVoy
2022-09-07 1:40 ` steve jenkin
2022-09-07 2:33 ` segaloco via TUHS
2022-09-07 4:08 ` Steve Jenkin
2022-09-07 13:08 ` Steffen Nurpmeso
2022-09-07 14:56 ` Larry McVoy
2022-09-07 21:27 ` Steve Jenkin
2022-09-07 22:36 ` Larry McVoy [this message]
2022-09-08 14:42 ` Paul Winalski
2022-09-08 15:02 ` Larry McVoy
2022-09-08 15:04 ` ron minnich
2022-09-08 15:52 ` Warner Losh
2022-09-08 16:47 ` Paul Winalski
2022-09-08 16:50 ` segaloco via TUHS
2022-09-08 17:58 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2022-09-06 19:04 Douglas McIlroy
2022-09-05 23:48 [TUHS] " steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07 4:00 ` steve jenkin
2022-09-07 14:58 ` John Cowan
2022-09-07 17:13 ` Paul Winalski
2022-09-08 14:12 ` Paul Winalski
2022-09-07 5:15 ` steve jenkin
2022-09-07 13:20 ` Dan Cross
2022-09-07 13:52 ` Steve Nickolas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220907223605.GS31856@mcvoy.com \
--to=lm@mcvoy.com \
--cc=sjenkin@canb.auug.org.au \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).