From owner-freebsd-current@FreeBSD.ORG Fri Jul 6 03:29:04 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F200016A41F; Fri, 6 Jul 2007 03:29:04 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id D7B1F13C468; Fri, 6 Jul 2007 03:29:02 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 6A284B09; Thu, 5 Jul 2007 21:56:19 -0500 (CDT) Date: Thu, 5 Jul 2007 21:56:19 -0500 To: jmg@FreeBSD.org, current@FreeBSD.org Message-ID: <20070706025619.GA19556@soaustin.net> References: <200707051428.22766.jhb@freebsd.org> <200707052245.l65MjpmR055403@fire.js.berklix.net> <20070706022631.GQ1221@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070706022631.GQ1221@funkthat.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Fri, 06 Jul 2007 11:45:31 +0000 Cc: Subject: Re: Code removal - Was Re: Future of the ie(4) driver 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: Fri, 06 Jul 2007 03:29:05 -0000 > I'm sure even if we push it to a News item and send it out to > -announce there'll be someone who said, "Why didn't I get a personally > couriered letter to my home, my place of business and my vacation > home?" Although IMHO you are slightly overstating this, I will note that even with a well-documented ports deprecation process (ports are tagged for ~2 months, notification emails are sent to ports@), there will always be someone who doesn't get the message. You cannot optimize for complete notification. We can go crazy with policies. A sensible compromise is needed; the ports experience suggests that "sufficient notification" will make the least people unhappy (for some value of "sufficient"). Now I'll put on my bugmeister hat and say that I'd rather see see effort devoted to clearing up PRs about hardware that is widespread, rather than spending time on obsolete hardware. If we didn't have much more of the former than we have developer time to work on, I might be more sympathetic. mcl