From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZSqzf-0002sA-Qo for mharc-grub-devel@gnu.org; Fri, 21 Aug 2015 14:24:48 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59006) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSqzc-0002mi-I4 for grub-devel@gnu.org; Fri, 21 Aug 2015 14:24:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZSqzU-00020y-VV for grub-devel@gnu.org; Fri, 21 Aug 2015 14:24:40 -0400 Received: from mail-lb0-x22b.google.com ([2a00:1450:4010:c04::22b]:34877) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSqzU-000204-OJ for grub-devel@gnu.org; Fri, 21 Aug 2015 14:24:36 -0400 Received: by lbcbn3 with SMTP id bn3so48557419lbc.2 for ; Fri, 21 Aug 2015 11:24:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rCpvMTyj9THfXd+VoRclBsjGD3Pn4udbBkJoxNz3kIk=; b=CR+pHE48Vi2ndsD9tGUIwVVBRGyY4c6HhkNl1dF6vpFQvu3S1peDLogd5xgl9kbG4H 7YZvS0MEoMPUopEoN5eyzhsbN8aZs3w3UZqTPHwpfpVZqw8NW9KwBcmyJHBsBwVs9qrQ nf/6fj62EpYX9eKyFYP8TlBxLck5m8vjX6iHhNeZxS95E6KjqKEgHYoBz8HkszTrGfEG KDzEMqA3bQOC6pDH0iu0B0ClTTrD2y5mlTWeKgybggzP7XDz+AShcm+A9qdHTDhVUuJC m6rJxwKgxnR+f0zAyz9qzgxs59so6ez/4hYvVd9ctALAE5BjMh18mTeAF1tg5oL17m4/ jAOQ== X-Received: by 10.112.42.172 with SMTP id p12mr8861494lbl.52.1440181475027; Fri, 21 Aug 2015 11:24:35 -0700 (PDT) Received: from [192.168.1.43] (ppp91-76-5-127.pppoe.mtu-net.ru. [91.76.5.127]) by smtp.gmail.com with ESMTPSA id jc10sm2511491lac.12.2015.08.21.11.24.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Aug 2015 11:24:34 -0700 (PDT) Message-ID: <55D76CE1.6040204@gmail.com> Date: Fri, 21 Aug 2015 21:24:33 +0300 From: Andrei Borzenkov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: The development of GNU GRUB Subject: Re: GRUB release schedule? References: <20150720182245.GC14894@redhat.com> <55D7585B.7090508@fb.com> <20150821171142.GM26663@l.oracle.com> In-Reply-To: <20150821171142.GM26663@l.oracle.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::22b 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:24:46 -0000 21.08.2015 20:11, Konrad Rzeszutek Wilk пишет: > 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? > > 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? >> GRUB includes comprehensive amount of regression tests. Just run "make check". The practical problems are - many tests require additional tools (filesystem tests need at least mkfs for respective file system, LVM etc) - each platform must be built separately; that requires either native system or cross tools (which itself may not be trivial). So I e.g. am limited to x86 - tests are not really formalized, you get PASS/FAIL but what failed is up to human to understand - some tests require server part, e.g. to run anything involving HTTP server must be available - some tests are pretty heavy hit; it is better now when I have new hardware still I cannot dream running them continuously on my notebook ... Of course addition to regression testing is always welcome.