From owner-freebsd-current@FreeBSD.ORG Mon Jun 6 14:31:26 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7389216A41C; Mon, 6 Jun 2005 14:31:26 +0000 (GMT) (envelope-from security@t-hosting.hu) Received: from viefep12-int.chello.at (viefep12-int.chello.at [213.46.255.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F47743D53; Mon, 6 Jun 2005 14:31:24 +0000 (GMT) (envelope-from security@t-hosting.hu) Received: from [80.98.207.149] by viefep12-int.chello.at (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050606143123.ZQRQ2846.viefep12-int.chello.at@[80.98.207.149]>; Mon, 6 Jun 2005 16:31:23 +0200 Message-ID: <42A45E46.40903@t-hosting.hu> Date: Mon, 06 Jun 2005 16:31:34 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lars Erik Gullerud References: <42A11C92.5050505@samsco.org> <20050605023739.J42933@lexi.siliconlandmark.com> <20050605221438.L43170@Neo-Vortex.net> <20050605124250.GA691@pato.euesrg02.net> <42A33262.4020005@makeworld.com> <20050605171914.GA16327@gothmog.gr> <86is0r7ep1.fsf@xps.des.no> <20050606161942.F17627@electra.nolink.net> In-Reply-To: <20050606161942.F17627@electra.nolink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , Chris , freebsd-current@freebsd.org, Giorgos Keramidas Subject: Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 06 Jun 2005 14:31:26 -0000 > So you are saying there will never be a 6.0-RELEASE, since releases > are normally tagged e.g. RELENG_5_4, and one would therefore expect a > RELENG_6_0 for the -RELEASE? > First, the RELENG_6 will be tagged, it will be the frozen state of the HEAD. When 6.0-RELEASE gets released, the release state will be tagged to RELENG_6_0_RELEASE and then, the RELENG_6 becomes the 6-STABLE branch, and the HEAD becomes 7-CURRENT. From this point the security patches from 6-STABLE or 7-CURRENT will be backported to the release state, and this will be tagged as RELENG_6_0, so one can just checkout only the security patches and rebuild the system from source. Cheers, Gábor