From owner-freebsd-chat Thu Jun 29 1:28:15 2000 Delivered-To: freebsd-chat@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 6638637BBAE for ; Thu, 29 Jun 2000 01:27:53 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 137Zey-000GIK-00; Thu, 29 Jun 2000 10:26:56 +0200 Date: Thu, 29 Jun 2000 10:26:56 +0200 From: Neil Blakey-Milner To: Brett Glass Cc: cjclark@alum.mit.edu, Brooks Davis , Francisco Reyes , FreeBSd Chat list Subject: Re: Why can't upgrades be simpler? Message-ID: <20000629102655.A62528@mithrandr.moria.org> References: <4.3.2.7.2.20000628112835.00de8710@localhost> <4.3.2.7.2.20000627131107.0449d500@localhost> <200006270352.XAA29208@sanson.reyes.somos.net> <200006270352.XAA29208@sanson.reyes.somos.net> <20000626232045.A17065@orion.ac.hmc.edu> <4.3.2.7.2.20000627131107.0449d500@localhost> <20000628095257.A44982@mithrandr.moria.org> <4.3.2.7.2.20000628112835.00de8710@localhost> <20000628215142.C451@dialin-client.earthlink.net> <4.3.2.7.2.20000629021220.04f8ae40@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <4.3.2.7.2.20000629021220.04f8ae40@localhost>; from brett@lariat.org on Thu, Jun 29, 2000 at 02:14:23AM -0600 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu 2000-06-29 (02:14), Brett Glass wrote: > At 10:51 PM 6/28/2000, Crist J. Clark wrote: > > >You are one of the proponents of keeping STABLE as "stable" as > >possible. We all have heard several times that you never start using a > >new release until x.2. Now, you want the active development done on > >this stable branch? It seems that you want to have your cake and eat > >it too (to use a cliche that never made much sense to me). > > There should be more active POLISHING on the stable branch before each > divergence. From .0 to about .2. (Heck, if this were done, it might > well be that .1 was really solid enough for production work.) What sort of things are you talking about? Almost all changes should go through -CURRENT before being applied, but there can certainly be exceptions for well-tested, verified, script(1)'d make release'd code. Again, you know where to send your patches. You can't mandate that committers perform this polishing (or anything really) for you. However, if a committer wishes to polish, I doubt anyone would object if it was done in a consistent manner with sufficient testing and review. (I'd recommend a multiprocessor machine with lots of memory, running constant make -j16 releases) Really, give some examples of cases where things can't be done via -CURRENT, and you'll get more response. Describing a possible flaw in the system where there has never been any requests in that area doesn't indicate a flaw, but rather that noone is requesting things in that area. When reasonable, competent, and reviewed requests _do_ come in, and aren't answered, then I'd encourage you to bring this up again. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message