From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZSrGR-0008WT-KN for mharc-grub-devel@gnu.org; Fri, 21 Aug 2015 14:42:07 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35296) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSrGP-0008Vz-4U for grub-devel@gnu.org; Fri, 21 Aug 2015 14:42:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZSrGK-0001Ve-4K for grub-devel@gnu.org; Fri, 21 Aug 2015 14:42:05 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:41435) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSrGJ-0001Va-U4 for grub-devel@gnu.org; Fri, 21 Aug 2015 14:42:00 -0400 Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t7LIfwQC011746 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 21 Aug 2015 18:41:59 GMT Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id t7LIfwmC006424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 21 Aug 2015 18:41:58 GMT Received: from abhmp0019.oracle.com (abhmp0019.oracle.com [141.146.116.25]) by aserv0122.oracle.com (8.13.8/8.13.8) with ESMTP id t7LIfwu4009186 for ; Fri, 21 Aug 2015 18:41:58 GMT Received: from l.oracle.com (/10.137.176.158) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 21 Aug 2015 11:41:58 -0700 Received: by l.oracle.com (Postfix, from userid 1000) id 914556A3C36; Fri, 21 Aug 2015 14:41:57 -0400 (EDT) Date: Fri, 21 Aug 2015 14:41:57 -0400 From: Konrad Rzeszutek Wilk To: The development of GNU GRUB Subject: Re: GRUB release schedule? Message-ID: <20150821184157.GB1948@l.oracle.com> References: <20150720182245.GC14894@redhat.com> <55D7585B.7090508@fb.com> <20150821171142.GM26663@l.oracle.com> <55D76CE1.6040204@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <55D76CE1.6040204@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Content-Transfer-Encoding: quoted-printable X-Source-IP: aserv0021.oracle.com [141.146.126.233] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 141.146.126.69 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 18:42:06 -0000 On Fri, Aug 21, 2015 at 09:24:33PM +0300, Andrei Borzenkov wrote: > 21.08.2015 20:11, Konrad Rzeszutek Wilk =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >On Fri, Aug 21, 2015 at 09:56:59AM -0700, Josef Bacik wrote: > >>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 be= ta > >>>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 rec= tify > >>>which ones aren't upstream vs which ones have been fixed upstream wi= th > >>>/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 reg= ular > >>>cadence? What needs to be done to make regular releases happen? Go= ing > >>>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 t= here'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 build= s > >>rather than running from git. Thanks, > > > >What is the tests that are needed? Surely as different distros we coul= d > >pool some hardware together to make this work? > > > >What do GRUB maintainers think are the top tests that are needed and > >on what architectures? And do you have any ideas on how to automate it= ? > >> >=20 > GRUB includes comprehensive amount of regression tests. Just run "make > check". The practical problems are >=20 > - many tests require additional tools (filesystem tests need at least m= kfs > for respective file system, LVM etc) >=20 > - each platform must be built separately; that requires either native s= ystem > or cross tools (which itself may not be trivial). So I e.g. am limited = to > x86 >=20 > - tests are not really formalized, you get PASS/FAIL but what failed is= up > to human to understand >=20 > - some tests require server part, e.g. to run anything involving HTTP s= erver > must be available >=20 > - some tests are pretty heavy hit; it is better now when I have new har= dware > still I cannot dream running them continuously on my notebook ... >=20 > Of course addition to regression testing is always welcome. Lets start with a list of priorities: - What are the most important platforms after x86? - What are the most important tests that MUST PASS all the time? - Which ones have been FAILing for years?=20 Surely if we weed out the most important cases that cover 99% that will give the foundation for going out with a release? >=20 > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel