Date: Wed, 25 Jun 2008 12:21:21 -0700 From: Jo Rhett <jrhett@netconsonance.com> To: Peter Wemm <peter@wemm.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, John Baldwin <jhb@freebsd.org> Subject: Re: tracking -stable in the enterprise Message-ID: <15C7C9E0-7F99-4FAC-941A-9BBCC3600E55@netconsonance.com> In-Reply-To: <e7db6d980806250346q2871abd3n2147b936155cc4e2@mail.gmail.com> References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <200806231051.03685.jhb@freebsd.org> <A27FDCBE-2C4E-49A5-8826-2FB47E2FEA3E@netconsonance.com> <e7db6d980806250346q2871abd3n2147b936155cc4e2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 25, 2008, at 3:46 AM, Peter Wemm wrote: > 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. Okay, that makes sense to me ;-) >> 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 > 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. Yes, we are definitely on the same page. Thanks for the clarification ;-) > We don't upgrade machines that have been deployed unless there is a > good reason to. Do you deploy machines for longer than 1 year? How do you deal with security patches in the longer term? -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15C7C9E0-7F99-4FAC-941A-9BBCC3600E55>