Date: Mon, 06 Jun 2005 16:31:34 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <security@t-hosting.hu> To: Lars Erik Gullerud <lerik@nolink.net> Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, Chris <racerx@makeworld.com>, freebsd-current@freebsd.org, Giorgos Keramidas <keramida@freebsd.org> Subject: Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot Message-ID: <42A45E46.40903@t-hosting.hu> In-Reply-To: <20050606161942.F17627@electra.nolink.net> References: <42A11C92.5050505@samsco.org> <a9eb3585050604155676d82e7e@mail.gmail.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42A45E46.40903>