Date: Tue, 19 Nov 2002 10:49:21 -0400 (AST) From: "Marc G. Fournier" <scrappy@hub.org> To: Vallo Kallaste <kalts@estpak.ee> Cc: "Sameer R. Manek" <manek@ecst.csuchico.edu>, <freebsd-stable@FreeBSD.ORG>, <re@FreeBSD.ORG> Subject: Re: restoring definition of -stable Message-ID: <20021119104221.M19853-100000@hub.org> In-Reply-To: <20021119143531.GA1770@tiiu.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Nov 2002, Vallo Kallaste wrote: > On Mon, Nov 18, 2002 at 02:36:00PM -0800, "Sameer R. Manek" > <manek@ecst.csuchico.edu> wrote: > > > cc'd to release engineering team > > > > I think part of the problem is that freebsd has lost someone who previously > > used to make sure that patches MFC were actually stable. JKH used to play an > > active role in that. I remember once, someone had MFC some code that > > introduced a stability bug, Jordan told the list that whoever MFCd' the code > > had till the end of the day to issue a fix, or roll back the patch. We all > > agree that -current is never a good idea for production systems. > > Actually, it weren't so beautiful, if I remember. Every so often in > the release cycle were pre-release commitfest by jkh, because almost > all the patches did through his hands. I'm not so sure he did > commit/test cycle on each patch, this is unrealistic considering it > as one-man job. Not that I want to diminish jkh long-time > contributions to FreeBSD Project, just making sure you all don't get > so excited about this model. Actually, major benefit to this model is that JKHs time was dedicated to the project, so if a patch did break something, he could dedicate the time to tracking down the person who committed (or submitted) the patch to get it fixed, or pull it out, accordingly ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021119104221.M19853-100000>