From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZSq95-0002r4-62 for mharc-grub-devel@gnu.org; Fri, 21 Aug 2015 13:30:27 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50485) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSq92-0002py-AI for grub-devel@gnu.org; Fri, 21 Aug 2015 13:30:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZSq8z-00032m-3o for grub-devel@gnu.org; Fri, 21 Aug 2015 13:30:24 -0400 Received: from userp1040.oracle.com ([156.151.31.81]:31848) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSq8y-00031g-U1 for grub-devel@gnu.org; Fri, 21 Aug 2015 13:30:21 -0400 Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t7LHUJM2009025 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 21 Aug 2015 17:30:20 GMT Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id t7LHUJnX003842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 21 Aug 2015 17:30:19 GMT Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id t7LHUJWp028479 for ; Fri, 21 Aug 2015 17:30:19 GMT Received: from l.oracle.com (/10.137.176.158) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 21 Aug 2015 10:30:19 -0700 Received: by l.oracle.com (Postfix, from userid 1000) id 5DD6B6A3C36; Fri, 21 Aug 2015 13:30:18 -0400 (EDT) Date: Fri, 21 Aug 2015 13:30:18 -0400 From: Konrad Rzeszutek Wilk To: The development of GNU GRUB Subject: Re: GRUB release schedule? Message-ID: <20150821173018.GA23640@l.oracle.com> References: <20150720182245.GC14894@redhat.com> <55D7585B.7090508@fb.com> <20150821171142.GM26663@l.oracle.com> <55D75D50.7050002@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55D75D50.7050002@fb.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Source-IP: userv0021.oracle.com [156.151.31.71] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 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 17:30:25 -0000 On Fri, Aug 21, 2015 at 10:18:08AM -0700, Josef Bacik wrote: > On 08/21/2015 10:11 AM, Konrad Rzeszutek Wilk wrote: > >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 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, > > > >What is the tests that are needed? Surely as different distros we could > >pool some hardware together to make this work? > > > > There was just some mention of tests failing earlier in the thread, that's > what I was talking about. Right. > > >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? > > We're automating testing internally by provisioning the different types of > boxes we have with grub2. Once I have the ipv6 and tcp window scaling stuff > in I plan to have continuous testing on grub2 to make sure our use case > doesn't get broken by somebody. Thanks, Fantastic! Would there by any way to get this reflector copied on the emails on the testing? > > Josef > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel