From owner-freebsd-current@FreeBSD.ORG Tue Nov 19 23:25:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A208B130 for ; Tue, 19 Nov 2013 23:25:22 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 60CA925CC for ; Tue, 19 Nov 2013 23:25:22 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ViufR-0001jK-TQ for freebsd-current@freebsd.org; Wed, 20 Nov 2013 00:25:13 +0100 Received: from cpc3-walt15-2-0-cust148.13-2.cable.virginm.net ([86.21.186.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Nov 2013 00:25:13 +0100 Received: from walterhurry by cpc3-walt15-2-0-cust148.13-2.cable.virginm.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Nov 2013 00:25:13 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Walter Hurry Subject: Re: 10.0-RELEASE cycle status update Date: Tue, 19 Nov 2013 23:24:52 +0000 (UTC) Lines: 7 Message-ID: References: <20131119162205.GW1643@glenbarber.us> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: cpc3-walt15-2-0-cust148.13-2.cable.virginm.net User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Cc: freebsd-stable@freebsd.org 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:25:22 -0000 On Tue, 19 Nov 2013 11:22:05 -0500, Glen Barber wrote: > As some may have noticed, the 10.0-RELEASE cycle has slipped a bit > behind schedule. No worries; release it when it's ready. Many thanks to all concerned for their efforts.