From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 14:41:06 2004 Return-Path: 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 B337716A4CE; Thu, 9 Dec 2004 14:41:06 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B47743D5D; Thu, 9 Dec 2004 14:41:06 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.1.102] (CPE000625f86c85-CM000e5c22aba0.cpe.net.cable.rogers.com [69.193.110.163] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB9EhDPx021106; Thu, 9 Dec 2004 07:43:14 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41B863FD.7000007@freebsd.org> Date: Thu, 09 Dec 2004 07:41:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org Subject: Wanted: lots of 6-CURRENT testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 09 Dec 2004 14:41:06 -0000 All, There has been an incredible amount of work going into 6-CURRENT in the last 5 weeks. With the holidays quickly approaching, now seems like a good time to step back and start really testing the system to shake out the bugs and catch the developers before they disappear for the holidays. In particular, the recent massive changes to the vnode layer and the upgrade of the net80211 layer and wireless lan drivers needs a lot of review and testing. Now is also a good time to review the recent additions to the PR database and start seeing if there are trends developing and/or areas that need immediate attention. While 6-CURRENT remains in a high state of flux I'll also ask that people carefully consider what to merge into 5-STABLE and when to merge it. Don't let important bugfixes that would benefit 5-STABLE and 4-STABLE drop on the floor, but also make sure that they recieve thorough testing before being merged back. Thanks, Scott