From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZSpdV-00079R-PX for mharc-grub-devel@gnu.org; Fri, 21 Aug 2015 12:57:49 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43661) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSpdT-00077y-Iv for grub-devel@gnu.org; Fri, 21 Aug 2015 12:57:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZSpdQ-0003Pn-7S for grub-devel@gnu.org; Fri, 21 Aug 2015 12:57:47 -0400 Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:46429) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSpdQ-0003PJ-2R for grub-devel@gnu.org; Fri, 21 Aug 2015 12:57:44 -0400 Received: from pps.filterd (m0004060 [127.0.0.1]) by mx0b-00082601.pphosted.com (8.14.5/8.14.5) with SMTP id t7LGvg4P018200 for ; Fri, 21 Aug 2015 09:57:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=message-id : date : from : mime-version : to : subject : references : in-reply-to : content-type : content-transfer-encoding; s=facebook; bh=pv6tJuuDF54YlpDgWhsW3SQY4A0Zl3aQDSEvgZNFhJs=; b=Cz0ltGDzgFwpzGTVIsErOCVlrDW1KcmcgL5mtxsLdKH0F5sGRyyD65/M316bCGR2PZ3P BD6ZboMpnR2XVo6vJNaEdPKQA8xNpHqmWZrjTUWh2Pd1kGU0HOKmwxZVePMtqO1ENsCx FWxWOa2l1Gg5ebeoAVpQ/3k0rVd5stFrWk8= Received: from mail.thefacebook.com ([199.201.64.23]) by mx0b-00082601.pphosted.com with ESMTP id 1we6r0rc79-4 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Fri, 21 Aug 2015 09:57:42 -0700 Received: from localhost.localdomain (192.168.52.123) by mail.thefacebook.com (192.168.16.19) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 21 Aug 2015 09:57:00 -0700 Message-ID: <55D7585B.7090508@fb.com> Date: Fri, 21 Aug 2015 09:56:59 -0700 From: Josef Bacik User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Subject: Re: GRUB release schedule? References: <20150720182245.GC14894@redhat.com> In-Reply-To: <20150720182245.GC14894@redhat.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.52.123] X-Proofpoint-Spam-Reason: safe X-FB-Internal: Safe X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-08-21_08:2015-08-21, 2015-08-21, 1970-01-01 signatures=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x X-Received-From: 67.231.153.30 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2015 16:57:48 -0000 On 07/20/2015 11:22 AM, Peter Jones wrote: > Hi everyone, > Is there a plan for when upcoming GNU GRUB releases will happen? > > As far as I can tell, the last official release on > ftp://ftp.gnu.org/gnu/grub/ was 2.00 on 28-Jun-2012, and the last beta > on http://alpha.gnu.org/pub/gnu/grub/ for the next version was > 2.02~beta2 on 24-Dec-2013 . There are (give or take) 471 patches > committed since that beta 18 months ago. > > In the mean time, nearly every Linux distro is shipping a package > derived from the 2.02~beta2 release plus some number of patches, > some from the upstream repo and some not, and it's cumbersome to rectify > which ones aren't upstream vs which ones have been fixed upstream with > /nearly/ the same patch, etc., with all the noise of so many patches > since the release. > > I suspect this would be better for a lot of GRUB users if releases > happened on a regular schedule, or if, relatively often (say once or > twice per year), a release schedule that spans several weeks and > organized some kind of alpha->beta->release progression were decided > upon and followed. > > So, can we make a release process that happens according to some regular > cadence? What needs to be done to make regular releases happen? Going > for years with the patch volume GRUB sees without doing a release is > really not good for anybody. > I'd like to +1 this. I think the tests are important for sure, but there's no reason we can't set a release cadence and at least cut an -rc1 and spend some time fixing up the test failures. Facebook is going to be using grub2 in our provisioning environment, we would like to have official builds rather than running from git. Thanks, Josef