From owner-freebsd-current Tue Sep 3 13:31:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA23635 for current-outgoing; Tue, 3 Sep 1996 13:31:54 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA23626 for ; Tue, 3 Sep 1996 13:31:47 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA27094; Tue, 3 Sep 1996 13:31:14 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma027057; Tue Sep 3 13:31:09 1996 Message-ID: <322C9545.446B9B3D@whistle.com> Date: Tue, 03 Sep 1996 13:29:57 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.org CC: rkw@dataplex.net Subject: -current in production.. (was food for thought) References: <199609031919.MAA04862@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk With all the hullabaloo about -current not being stable or always building.. I thought I 'd give a little report here.. I sup the CVS tree at 2AM each day. I rebuild a system a couple of times a week. when it seems stable, I take a Snapshot of the sources, and the rest of the company moves onto that snapshot.. It's very rare that I have to abandon a snapshot because it doesn't build. I've really very happy with teh current scheme.. I think it's just expectations.. 1/ I sup the CVS tree so I get more control 2/ I have a sacrificial machine/environment I can test it on first.. I have -current (1 week old in about a dozen machines here. I'll be upgrading to yesterday's probably.. I have 4 in the field, and expect to have many more in a few months.. I think curretn has been quite stable.. If it fails, I just wait a day.. julian