From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZIUTA-00064f-DT for mharc-grub-devel@gnu.org; Fri, 24 Jul 2015 00:20:24 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41349) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZIUT8-00064V-17 for grub-devel@gnu.org; Fri, 24 Jul 2015 00:20:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZIUT4-0003n8-Gi for grub-devel@gnu.org; Fri, 24 Jul 2015 00:20:21 -0400 Received: from mail-la0-x22e.google.com ([2a00:1450:4010:c03::22e]:33744) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZIUT4-0003kZ-9H for grub-devel@gnu.org; Fri, 24 Jul 2015 00:20:18 -0400 Received: by laah7 with SMTP id h7so6972272laa.0 for ; Thu, 23 Jul 2015 21:20:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=xbFYnOHaqLCtHNE9ShnL+rtU5MXuGBn9IBLEV9hweig=; b=xpToONxyzh1ws6Xvf8+2B5cASI+IOHfq1R4z2+30UJdfgMv1yU4ZNaWlL980lndAck LB6J+SXmM8COJyeC3Nfre93+GOkPp6oPk3XvH7Argx9j74HmydcoeIofSgPJE/jSsfXU /x5ju5L9SC9uPwQQyWtz1jlxn+AKu9eCcqYfeuZdjkAqzVWguddQcG/9e05M0k3nFNyA McqRy3KgcHTa4IVwAncIOGOM5mj0RvAaL3aOrTxQveSb3CyVg5Fxs+UVIIyUBeLMQxHi vkjdB6cXnGeXypWmtSCMY/NPxtxzXA0Cl7lHKrTwRqOgH6skQYv0tjMO8Xf0oRX4L2PK HXgw== X-Received: by 10.152.23.4 with SMTP id i4mr11557881laf.51.1437711616384; Thu, 23 Jul 2015 21:20:16 -0700 (PDT) Received: from opensuse.site (ppp91-76-6-204.pppoe.mtu-net.ru. [91.76.6.204]) by smtp.gmail.com with ESMTPSA id h3sm1460162lbj.19.2015.07.23.21.20.15 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Jul 2015 21:20:15 -0700 (PDT) Date: Fri, 24 Jul 2015 07:20:15 +0300 From: Andrei Borzenkov To: Peter Jones Subject: Re: GRUB release schedule? Message-ID: <20150724072015.0a5ac66a@opensuse.site> In-Reply-To: <20150720182245.GC14894@redhat.com> References: <20150720182245.GC14894@redhat.com> X-Mailer: Claws Mail 3.11.0 (GTK+ 2.24.28; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::22e Cc: grub-devel@gnu.org 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, 24 Jul 2015 04:20:23 -0000 =D0=92 Mon, 20 Jul 2015 14:22:45 -0400 Peter Jones =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > Hi everyone, > Is there a plan for when upcoming GNU GRUB releases will happen? >=20 > 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. >=20 > 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. >=20 > 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. >=20 > So, can we make a release process that happens according to some regular > cadence? What needs to be done to make regular releases happen? Apart from having more active contributors? :) Automating build and regression tests would definitely help it. > Going > for years with the patch volume GRUB sees without doing a release is > really not good for anybody. >=20