grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB release schedule?
Date: Wed, 29 Jul 2015 14:01:46 -0500	[thread overview]
Message-ID: <55B9231A.2070105@gmail.com> (raw)
In-Reply-To: <55B00C76.5060808@gmail.com>

Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 20.07.2015 21:25, Vladimir 'phcoder' Serbinenko wrote:
>> I'll do next beta tomorrow and will assess current open bugs to see how
>> far we're from release
>>
> Fixing tests takes longer than expected. I'll continue tomorrow.

Any more on this?

>> Le 20 juil. 2015 20:23, "Peter Jones" <pjones@redhat.com
>> <mailto:pjones@redhat.com>> a écrit :
>>
>>      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.

I agree.

   -- Bruce Dubbs
      linuxfromscratch.org



  reply	other threads:[~2015-07-29 19:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 18:22 GRUB release schedule? Peter Jones
2015-07-20 19:25 ` Vladimir 'phcoder' Serbinenko
2015-07-22 21:34   ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-07-29 19:01     ` Bruce Dubbs [this message]
2015-07-29 19:14       ` Vladimir 'phcoder' Serbinenko
2015-12-08 20:55   ` Peter Jones
2015-12-08 21:34     ` Josef Bacik
2015-07-24  4:20 ` Andrei Borzenkov
2015-07-24  8:03   ` Vladimir 'phcoder' Serbinenko
2015-07-24 10:59     ` Andrei Borzenkov
2015-08-21 16:56 ` Josef Bacik
2015-08-21 17:11   ` Konrad Rzeszutek Wilk
2015-08-21 17:18     ` Josef Bacik
2015-08-21 17:30       ` Konrad Rzeszutek Wilk
2015-08-21 17:57         ` Josef Bacik
2015-08-21 18:24     ` Andrei Borzenkov
2015-08-21 18:41       ` Konrad Rzeszutek Wilk
2015-08-21 19:55         ` Bruce Dubbs
2015-08-22  5:19           ` Andrei Borzenkov
2015-08-22  5:16         ` Andrei Borzenkov
2015-08-24 18:20           ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2020-10-25 16:59 Bruce Dubbs
2020-10-26 14:27 ` Daniel Kiper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55B9231A.2070105@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).