From owner-freebsd-stable@FreeBSD.ORG Thu Jul 21 11:21:02 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE43216A41F for ; Thu, 21 Jul 2005 11:21:02 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87D1843D83 for ; Thu, 21 Jul 2005 11:21:00 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id DC854A2FCA; Thu, 21 Jul 2005 13:20:59 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id AE3586462; Thu, 21 Jul 2005 13:20:59 +0200 (CEST) Date: Thu, 21 Jul 2005 13:20:59 +0200 From: Marc Olzheim To: Daniel O'Connor Message-ID: <20050721112059.GA52753@stack.nl> References: <1121917413.4895.47.camel@localhost.localdomain> <20050721095732.GG52120@stack.nl> <200507212029.47615.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <200507212029.47615.doconnor@gsoft.com.au> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Marc Olzheim , Alexey Yakimovich , freebsd-stable@freebsd.org Subject: Re: Quality of FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2005 11:21:03 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 21, 2005 at 08:29:47PM +0930, Daniel O'Connor wrote: > I think the best way to rectify this is to test RC candidates on YOUR=20 > hardware.. This finds the bugs you need fixed at a time when people are v= ery=20 > receptive to fixing them. >=20 > It's not realistic for the release engineer to test on a lot of hardware = as=20 > they are very busy doing other things. Of course. That's why we test stuff first, before upgrading. However, real world situations are always different from test setups and the kind of race conditions that we're talking about that we were troubled by didn't show up until we had it in production... But that's why I always try to supply code to trigger the bug in my PRs after finding it, so that it can be tested for a next release. It's just that "this will probably not be fixed in 5.x" is not the thing I like to hear. But as said, there's always 4.x, which is the most stable OS I've seen in my open source UN*X life. Too bad that with 4.x I get responses on libc_r's uthread like "libc_r is dead, please use KSE", which don't help anyway. No need to burn your ships behind you just yet. (Or whatever the expression is in English) Marc --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC34UbezjnobFOgrERAozzAJ4h5LadohuvyXReqqkmREsJp1zYIgCfcDnI YyHwb4e9tkhP26ZBtWZFbGk= =N9vI -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1--