Date: Tue, 13 May 2003 16:07:24 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: Heiko Schaefer <hschaefer@fto.de> Cc: current@FreeBSD.org Subject: Re: 5.1-RELEASE TODO Message-ID: <Pine.NEB.3.96L.1030513160443.72145a-100000@fledge.watson.org> In-Reply-To: <20030513215348.K14785@daneel.foundation.hs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 May 2003, Heiko Schaefer wrote: > > That said, we are actively discussing what, if any, workarounds are > > appropriate, including some alternative workarounds from the ones > > currently present. > > bosko (who was mentioned here various time, regarding a patch to work > around this) has contacted me, and i am looking forward to try his > patch. assuming that the patch is correct (whatever that would mean in > this context), and there is some chance of accepting it anytime soon, > maybe it would be sensible to try to get that into the release - or > delay the release until this is sorted out ?! > > wouldn't a release that corrupts data in many, relevant, cases (i > consider the box i had the trouble with entirely mainstream) be worse > than no release at all? You don't need to argue to me that we need stability (I'm a fan of it myself): what I need is evidence that some set of changes is actually solving the problem, not masking it. If there exists a patch that substantially improves stability on some set of systems (and not at the cost of another set), I think you can rest assured that we'll get it into the release. As with you, we're very concerned by the recent spate of instability, especially in the beta cycle, and how to address that is very much on our minds. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030513160443.72145a-100000>