From owner-freebsd-stable@freebsd.org Sun Apr 3 03:12:14 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D263FB001DE for ; Sun, 3 Apr 2016 03:12:14 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BBDA91317 for ; Sun, 3 Apr 2016 03:12:14 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id u332kiLD095919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 2 Apr 2016 19:46:47 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id u332kiBD095918; Sat, 2 Apr 2016 19:46:44 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA11512; Sat, 2 Apr 16 18:57:15 PST Date: Sat, 02 Apr 2016 19:57:14 -0700 From: perryh@pluto.rain.com (Perry Hutchison) To: jack@jarasoft.net Cc: freebsd-stable@freebsd.org Subject: Re: Where is 10.2-STABLE? Message-Id: <5700868a.rBda67FHhYefo7xZ%perryh@pluto.rain.com> References: <64862.1459379077@server1.tristatelogic.com> <201603312254.u2VMsESi099019@gw.catspoiler.org> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2016 03:12:14 -0000 Jack Raats wrote: > If you look at the ftp.freebsd.org than you can see that > the 10.3-RELEASE can be downloaded. > The strange thing is that there is no announcement yet. The likely (short) explanation is that re@ are not entirely done with it. Before it can be announced, both the bits and all associated infrastructure have to be ready.