From owner-freebsd-current@FreeBSD.ORG Sat Dec 17 23:46:48 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C39F216A41F; Sat, 17 Dec 2005 23:46:48 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C43DF43D8D; Sat, 17 Dec 2005 23:46:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 349321A3C27; Sat, 17 Dec 2005 15:46:28 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6E2E751257; Sat, 17 Dec 2005 18:46:27 -0500 (EST) Date: Sat, 17 Dec 2005 18:46:27 -0500 From: Kris Kennaway To: Joe Rhett Message-ID: <20051217234627.GB68713@xor.obsecurity.org> References: <43A266E5.3080103@samsco.org> <20051217220021.GB93998@svcolo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline In-Reply-To: <20051217220021.GB93998@svcolo.com> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, current Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 23:46:48 -0000 --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 17, 2005 at 02:00:21PM -0800, Joe Rhett wrote: > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: > > There will be three FreeBSD 6 releases in 2006. >=20 > While this is nice, may I suggest that it is time to put aside/delay one > release cycle and come up with a binary update mechanism supported well by > the OS? Increasing the speed of releases is good. Increasing the number > of deployed systems out of date because there are no easy binary upgrade > mechanisms is bad. >=20 > It has been bad, it's getting worse. Suggestions are nice, but who do you think will work on solving this? Kris --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDpKNTWry0BWjoQKURArrgAJ46xm5kLCiEpGDtHeWHA8L3fkjMCgCeLTiu UfX7Pm71Cu1oNGyQ+QHj3vc= =Qoqa -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb--