From owner-freebsd-stable@FreeBSD.ORG Thu Mar 19 09:51:47 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B0ED1065676; Thu, 19 Mar 2009 09:51:47 +0000 (UTC) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (raats.xs4all.nl [82.95.230.43]) by mx1.freebsd.org (Postfix) with ESMTP id E1E918FC13; Thu, 19 Mar 2009 09:51:46 +0000 (UTC) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (localhost.jarasoft.net [127.0.0.1]) by raats.xs4all.nl (Postfix) with ESMTP id 7697522EDD; Thu, 19 Mar 2009 10:51:59 +0100 (CET) Received: from jara3 (unknown [10.10.10.20]) by raats.xs4all.nl (Postfix) with ESMTPA id 3AB6422A2F; Thu, 19 Mar 2009 10:51:59 +0100 (CET) Message-ID: <997A6168643B453CB90D2A25AD7AE563@jarasoft.net> From: "Jack Raats" To: "Robert Watson" References: <1237299551.80881.16.camel@bauer.cse.buffalo.edu><20090318102134.D55869@ns1.as.pvp.se> <91210A8474CD444786833AFD3542BCCA@jarasoft.net> Date: Thu, 19 Mar 2009 10:51:45 +0100 Organization: JaRaSoft, Steenbergen, Nederland MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Relayed-By: GPGrelay Version 0.959 (Win32) X-Virus-Scanned: ClamAV using ClamSMTP on orac.jarasoft.net Cc: kama , Ken Smith , freebsd-stable Subject: Re: FreeBSD 7.2 Release process starting... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jack Raats List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2009 09:51:47 -0000 From: "Robert Watson" >> About FreeBSD 6.4. If you consider to make new 6.4 iso's, perhaps it >> would be better to think about an 6.5 release???? > > It's a question of bandwidth for the release engineering team, ports team, > security officer team, etc -- I think a 6.5 is pretty much out of the > question right now with 8.0 preparing to ramp up and 7.2 now in flight. > That gives us a short menu of options: > > - Errata patches > - Errata patches + ISO reroll > - Point release > > Because of the boot loader issues, errata patches don't really cut it > alone, as if you can't install, you definitely can't apply errata patches > :-). This suggests a reroll or a point release. This reminds me of FreeBSD 4.6 and FreeBSD 4.6.2 (The first FreeBSD I ever used was 4.6, that's why I remember) > For me the distinction remains fuzzy, but I think a key to either approach > would be avoiding having to fully re-QA, do BETAs, build new packages, > etc. This suggests taking RELENG_6_4 on some date, perhaps rebranching if > it's a point release, or not if it's an ISO reroll, and bundling it with > exactly the same packages we shipped in 6.4 (etc) and bumping a few > documentation parts. Indeed, that's a lot of work for an errata patch. Jack