From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 10:38:59 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 648E116A407 for ; Wed, 13 Sep 2006 10:38:59 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 958DF43D45 for ; Wed, 13 Sep 2006 10:38:58 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tedgnm@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8DAcpa0068954 for ; Wed, 13 Sep 2006 12:38:57 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8DAcpc7068953; Wed, 13 Sep 2006 12:38:51 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 12:38:51 +0200 (CEST) Message-Id: <200609131038.k8DAcpc7068953@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <4507D7FB.7030404@antiszoc.hu> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 12:38:57 +0200 (CEST) Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG 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:38:59 -0000 Andras Gót wrote: > Oliver Fromme wrote: > > kama wrote: > > > 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. > > Sure but it's only a schedule. That's true, and the schedule will most probably change. Currently the release is listed for Oct. 9th, but I bet that it'll be delayed. > 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. Yes, which will be announced when BETA state begins, I assume. PRERELEASE isn't BETA (yet). > And an other main purpose is to do planning of the upgrade Uhm, would you please explain? What kind of upgrade depends on entering the pre-release state? When you're tracking -stable, then now is neither better nor worse a time for updating, except for the fact that -- due to the code freeze -- the code might have a tendency to stabilize better than before, because MFCs and commits that aren't bug fixes are held off. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard." -- Peter van der Linden