From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 01:26:52 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C13441065673 for ; Sat, 21 Jan 2012 01:26:52 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from services.syscare.sk (services.syscare.sk [188.40.39.36]) by mx1.freebsd.org (Postfix) with ESMTP id 1D5058FC16 for ; Sat, 21 Jan 2012 01:26:52 +0000 (UTC) Received: from services.syscare.sk (services [188.40.39.36]) by services.syscare.sk (Postfix) with ESMTP id 4F963A6F0F for ; Sat, 21 Jan 2012 02:07:23 +0100 (CET) X-Virus-Scanned: amavisd-new at rulez.sk Received: from services.syscare.sk ([188.40.39.36]) by services.syscare.sk (services.rulez.sk [188.40.39.36]) (amavisd-new, port 10024) with ESMTP id SnsjtdJvdFD8 for ; Sat, 21 Jan 2012 02:07:21 +0100 (CET) Received: from [172.17.2.102] (59576.ba.3pp.slovanet.sk [84.16.39.226]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: danger@rulez.sk) by services.syscare.sk (Postfix) with ESMTPSA id 07561A6EFB for ; Sat, 21 Jan 2012 02:07:20 +0100 (CET) Message-ID: <4F1A0FD7.2020604@FreeBSD.org> Date: Sat, 21 Jan 2012 02:07:35 +0100 From: Daniel Gerzo Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.2.25pre) Gecko/20111115 Lanikai/3.1.17pre MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4F153AE3.9010602@my.gd> <20120120133826.GB16676@FreeBSD.org> <4F196F9B.3050506@my.gd> <20120120135936.GC16676@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD has serious problems with focus, longevity, and lifecycle X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 01:26:52 -0000 On 20.1.2012 18:58, Freddie Cash wrote: >> It cannot be merged into RELEASE! RELEASE is a point on a branch, >> as soon as RELEASE had been released, you can't push anything into >> it, unless you have a time machine. > > I think he's asking "what's the criteria to push a patch to > RELENG_8_2, the security/fixes branch of -RELEASE?" IOW, how does one > increase the patch level (8.2-RELEASE-p5 -> 8.2-RELEASE-p6, etc) of a > release? > > I believe, and RE/security team can correct me on this, that the > criteria is along the lines of "security issues and major bug fixes > only". Perhaps that policy should be looked at and loosened slightly > to also include "driver updates"? Or something along those lines? > Perhaps look at releasing point releases (8.2.1) like DoubB suggested? I have already said it in this thread - I believe we should consider issuing much more errata notices (i.e. -pX); with that I mean we should consider more bugs as "major bugs". I don't really see a reason why not. And we should also provide some mechanism to allow for cherry-picking individual errata notices to be applied on the given release (e.g. p1, p2, p5, but not p3, p4). I don't think it makes sense to issue errata notices for driver updates as in support for new devices because we don't ship installation media with these patches applied. In those cases we would need to make those "point" releases. On the other hand, simply releasing minor releases more often would solve that problem too. -- S pozdravom / Best regards Daniel Gerzo, FreeBSD committer