From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 10:02:43 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG 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 103DA16A407 for ; Wed, 13 Sep 2006 10:02:43 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from andrej.mine.nu (catv-50634715.catv.broadband.hu [80.99.71.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C92943D45 for ; Wed, 13 Sep 2006 10:02:39 +0000 (GMT) (envelope-from andrej@antiszoc.hu) Message-ID: <4507D7FB.7030404@antiszoc.hu> Date: Wed, 13 Sep 2006 12:05:47 +0200 From: =?ISO-8859-1?Q?Andras_G=F3t?= User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <200609130921.k8D9LYxd063610@lurza.secnetix.de> In-Reply-To: <200609130921.k8D9LYxd063610@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 10:02:43 -0000 Oliver Fromme wrote: > kama wrote: > > I just updated the sources on two of my machines and found: > > > > $ uname -sr > > FreeBSD 6.2-PRERELEASE > > > > Is this a mistake or is it actually a prerelease? > > It's not a mistake. RELENG_6 has been frozen on Sep. 10th > in preparation of the upcoming 6.2-RELEASE, so it's now in > "pre-release" state. > > > Why isnt there any notice about it on the webpage > > or on this mailing list? > > It's on the webpage (under "Release Engineering"): > > http://www.freebsd.org/releng/ > > I don't think there's need to announce it on this mailing > list. The fact that RELENG_6 entered code-freeze is > important for comitters and (some) developers, but not for > normal users of the -stable branch. > > Best regards > Oliver > > Sure but it's only a schedule. The main purpose of the public release process would be that WE the users can see/check what are the problems that needs testing or anything. And an other main purpose is to do planning of the upgrade, if needed. I think I shouldn't have to remind you on this. :) Regards, Andras