From owner-freebsd-stable@FreeBSD.ORG Tue Oct 26 17:49:34 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AA5516A4FC; Tue, 26 Oct 2004 17:49:34 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30F8A43D4C; Tue, 26 Oct 2004 17:49:34 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i9QHoZBZ083065; Tue, 26 Oct 2004 11:50:36 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <417E8DC3.6080703@freebsd.org> Date: Tue, 26 Oct 2004 11:47:47 -0600 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: freebsd-current@freebsd.org, freebsd-stable@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: Plan for 5.3-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 17:49:34 -0000 All, Today was supposed to be the release day for 5.3, but some serious show-stoppers came to light yesterday. Since the purpose of 5.3 is to have a functionally stable release that is suitable for migrating to, we decided to hold up 5.3 until these issues are fixed. The first issue deals with TCP SACK problems that result in a livelocked system. The second involves GDB leaving threaded processes in an unkillable state. Fixes for both are under review and will be committed to RELENG_5 in a few days when preliminary testing is complete. I've also turned off ULE to help narrow down many of the ambiguous problems that are still being reported. ULE works fine for some, but it must be eliminated from the environment when you suspect a bug. I expect to keep ULE off in 5.x until the rate of other problem reports and decreased and someone takes an active interest in it. Please continue to test RC1. At this point I'm not going to promise a particular date for 5.3-RELEASE, but I would expect it in the next 7-10 days assuming nothing else significant comes up. Scott