From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 11:01:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27B3B1065672 for ; Wed, 25 Jun 2008 11:01:23 +0000 (UTC) (envelope-from peter@wemm.org) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.240]) by mx1.freebsd.org (Postfix) with ESMTP id E6A638FC1C for ; Wed, 25 Jun 2008 11:01:22 +0000 (UTC) (envelope-from peter@wemm.org) Received: by ag-out-0708.google.com with SMTP id 8so24309551agc.3 for ; Wed, 25 Jun 2008 04:01:22 -0700 (PDT) Received: by 10.100.201.9 with SMTP id y9mr18160094anf.60.1214390771488; Wed, 25 Jun 2008 03:46:11 -0700 (PDT) Received: by 10.100.154.11 with HTTP; Wed, 25 Jun 2008 03:46:11 -0700 (PDT) Message-ID: Date: Wed, 25 Jun 2008 03:46:11 -0700 From: "Peter Wemm" To: "Jo Rhett" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> Cc: FreeBSD Stable , John Baldwin Subject: Re: tracking -stable in the enterprise 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: Wed, 25 Jun 2008 11:01:23 -0000 On Wed, Jun 25, 2008 at 2:23 AM, Jo Rhett wrote: > On Jun 23, 2008, at 7:51 AM, John Baldwin wrote: >> >> FWIW, Yahoo! tracks -stable branches, not point releases. > > > I'm curious about this (and stealing the dead thread). > > How does one track -stable in an enterprise environment? I assume that what > you mean is "we pick points in -stable that we believe are stable enough and > create a snapshot from this point that we test and roll out to production" > ...? Am I wrong? Correct. We roll our own build snapshots periodically, but we also keep a pretty careful eye on what's going on in the -stable branches. When I say "we", I mostly mean John does it. :) Quite often the biggest factor that tells us when to roll a new internal release is when there's something that has gone into -stable that we want. We have many local modifications, so freebsd.org's concept of a "release" is pretty much meaningless to us. However, we do quietly help in freebsd.org's release process. We make a point of trying to run some recent snapshots in production in the leadup to a freebsd.org release. This helps shake out silly problems that might not get noticed in time. > I mean, I guess Yahoo has enough resources to literally run every commit to > -stable through a full test cycle and push it out to every machine, but my > mind boggles to imagine the manpower cost of doing so. (and to justify the > manpower cost versus the gain from doing so...) No. Why on earth would we do that? if we wanted to cause ourselves that much pain for no good reason, we'd go get a pencil and stab ourselves in the eye. We don't upgrade machines that have been deployed unless there is a good reason to. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell