From owner-freebsd-current@FreeBSD.ORG Tue Nov 19 23:03:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D8FCE877 for ; Tue, 19 Nov 2013 23:03:58 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id A32F3247A for ; Tue, 19 Nov 2013 23:03:58 +0000 (UTC) Received: from [96.28.178.143] ([96.28.178.143:34121] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id C6/07-29861-C5EEB825; Tue, 19 Nov 2013 23:03:57 +0000 Date: Tue, 19 Nov 2013 23:03:56 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: 10.0-RELEASE cycle status update References: <20131119162205.GW1643@glenbarber.us> X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Cc: Glen Barber X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 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: Tue, 19 Nov 2013 23:03:58 -0000 As some may have noticed, the 10.0-RELEASE cycle has slipped a bit behind schedule. > Here is where we stand at the moment: > - The iconv issues mentioned in a previous status update email[1] are > being looked at extensively. There are a number of iconv(3) fixes > that have been committed to head/, which are pending MFC to stable/10 > following the default 3-day merge period. Those tracking -CURRENT > are encouraged to update their systems and report back (on -current@) > any issues. Those awaiting the next 10.0 builds, please be patient. > We will have the next round of builds for the 10.0-RELEASE cycle > started as soon as possible. > [1] http://lists.freebsd.org/pipermail/freebsd-stable/2013-November/075658.html > Glen What are the symptoms I might look for on FreeBSD-current? Release engineering estimated dates ought to be updated on the website. Better to wait for a solid 10.0-RELEASE than rush to a buggy release. I am also concerned about the bug in re(4) driver. Tom