From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1a6Pu5-0000Q0-V1 for mharc-grub-devel@gnu.org; Tue, 08 Dec 2015 16:34:33 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54109) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6Pu3-0000Pm-F4 for grub-devel@gnu.org; Tue, 08 Dec 2015 16:34:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a6Pu0-0000ws-7I for grub-devel@gnu.org; Tue, 08 Dec 2015 16:34:31 -0500 Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:64606) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6Pu0-0000vY-26 for grub-devel@gnu.org; Tue, 08 Dec 2015 16:34:28 -0500 Received: from pps.filterd (m0001303.ppops.net [127.0.0.1]) by m0001303.ppops.net (8.15.0.59/8.15.0.59) with SMTP id tB8LVvRh003429 for ; Tue, 8 Dec 2015 13:34:22 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=subject : to : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=facebook; bh=d21ROY3E56kv2cCmm59E6sL9lEtCV5O7c9OW1LYI9Lo=; b=RxPmFfbQEVJ6TTlelMBOFdO6JbgyThJyl8JuZv8gyNcMl+bJGTTvJiZpqXSV9f83sDZm wESg1tDwOFnLo0XZ0f5ahSL1HlW8pS0ebJSLRVNaExX1KEOjD+sJAg89EOQIDCu+pKZk NdwZbNZatnbPzYGd8VPeDAv7yhwafDYTkZA= Received: from mail.thefacebook.com ([199.201.64.23]) by m0001303.ppops.net with ESMTP id 1ykvfgy1e7-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Tue, 08 Dec 2015 13:34:22 -0800 Received: from localhost.localdomain (192.168.54.13) by mail.thefacebook.com (192.168.16.20) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 8 Dec 2015 13:34:21 -0800 Subject: Re: GRUB release schedule? To: The development of GNU GRUB References: <20150720182245.GC14894@redhat.com> <20151208205556.GC5296@redhat.com> From: Josef Bacik Message-ID: <56674CDB.5000606@fb.com> Date: Tue, 8 Dec 2015 16:34:19 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20151208205556.GC5296@redhat.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.54.13] X-Proofpoint-Spam-Reason: safe X-FB-Internal: Safe X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2015-12-08_14:, , signatures=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] 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: Tue, 08 Dec 2015 21:34:32 -0000 On 12/08/2015 03:55 PM, Peter Jones wrote: > On Mon, Jul 20, 2015 at 09:25:56PM +0200, Vladimir 'phcoder' Serbinenko wrote: >> I'll do next beta tomorrow and will assess current open bugs to see how far >> we're from release > > Did this ever happen? It doesn't appear as though it did. > > So I'm back with my original question: What's the path to regular > releases? I don't honestly believe we have to fix everything about > source control, patch contribution, and test suites to do that, though > those are all important things. Plenty of projects do releases with the > same tools this one has, with great success. But this is one more case > where the search for perfection is stopping us from having any releases > *at all*. > > "Fix everything in the code *and* the infrastructure and then do a > release" is not workable. We need to have regular releases, and we need > to make improvements to the project's infrastructure and processes be a > part of those releases. Waiting for a flag day with each thing to be > improved just means delaying indefinitely, especially if the wish list > includes things nobody is actively working on. > > So that means we need two things: 1) decide on a schedule for one release, > 2) decide when the ones after it will be. > > Here's a suggestion: Schedule a release at the end of January, and work > towards that. It doesn't have to be perfect; everybody is shipping > something based on the current tree already anyway. Then plan on > another release at the end of July, and follow that plan indefinitely. > It's okay if there are reasons to adjust it sometimes, but let's start > with a plan. > > Thoughts? > I'd like to second this. ATM we're just running whatever is in my github copy of grub2, which I rebase whenever somebody tells me to. If we have consistent releases then it'll make it easier for me to run automated tests internally as well as have clear indicators when I need to rebase and figure out what outstanding patches I still have pending. Thanks, Josef