From owner-freebsd-qa Sat Sep 28 19:56:27 2002 Delivered-To: freebsd-qa@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F14BF37B401 for ; Sat, 28 Sep 2002 19:56:26 -0700 (PDT) Received: from pakastelohi.cypherpunks.to (pakastelohi.cypherpunks.to [213.130.163.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6523F43E6A for ; Sat, 28 Sep 2002 19:56:26 -0700 (PDT) (envelope-from shamrock@cypherpunks.to) Received: from VAIO650 (d160.nas2.sr2.sonic.net [208.201.229.160]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pakastelohi.cypherpunks.to (Postfix) with ESMTP id 13B7B36400 for ; Sun, 29 Sep 2002 04:56:24 +0200 (CEST) From: "Lucky Green" To: Subject: http://www.freebsd.org/releases/5.0R/schedule.html schedule error? Date: Sat, 28 Sep 2002 19:56:06 -0700 Message-ID: <002f01c26763$c3446d60$6501a8c0@VAIO650> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG http://www.freebsd.org/releases/5.0R/schedule.html shows 5.0 code freeze by October 20. However, the page also states that DP2 has so far been delayed by over 2 months since the code is not sufficiently stable to cut another DP. Given that, it is unclear to me how a November 20 release date for a rock-solid build could be met. I therefore was wondering if the RE team could perhaps please evaluate the present status of the 5.0 development effort and, if deemed appropriate, adjust the published schedule, in particular the release date, based on the results of this evaluation. Thanks, --Lucky Green To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message