From owner-freebsd-current@FreeBSD.ORG Thu Dec 22 21:10:43 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 69CBC16A422; Thu, 22 Dec 2005 21:10:43 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 226E643D45; Thu, 22 Dec 2005 21:10:41 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBMLAaQL081199; Thu, 22 Dec 2005 13:10:36 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBMLAKMd045889; Thu, 22 Dec 2005 13:10:20 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBMLAJVj045886; Thu, 22 Dec 2005 13:10:19 -0800 (PST) (envelope-from jrhett) Date: Thu, 22 Dec 2005 13:10:19 -0800 From: Jo Rhett To: Wilko Bulte Message-ID: <20051222211019.GI39174@svcolo.com> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051217220807.GA28741@freebie.xs4all.nl> Organization: svcolo.com User-Agent: Mutt/1.5.9i X-Mailman-Approved-At: Thu, 22 Dec 2005 21:13:58 +0000 Cc: stable@freebsd.org, current Subject: Re: HEADS UP: 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: Thu, 22 Dec 2005 21:10:43 -0000 On Sat, Dec 17, 2005 at 11:08:07PM +0100, Wilko Bulte wrote: > So, when will you fix it? Or hire someone to fix it? FreeBSD after > all is mostly a volunteer operation. I and many others have offered to work on this. The core team has repeatedly stated that they won't integrate the efforts, which makes os-upgrade capability minimal and easily broken. (see current efforts) -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation