All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Kiper <dkiper@net-space.pl>
To: grub-devel@gnu.org
Subject: Re: GRUB 2.06 release
Date: Fri, 29 May 2020 14:07:29 +0200	[thread overview]
Message-ID: <20200529120729.4qa7bonugkkuannp@tomti.i.net-space.pl> (raw)
In-Reply-To: <20200422102440.jtb2qmvw7zt6t42n@tomti.i.net-space.pl>

On Wed, Apr 22, 2020 at 12:24:40PM +0200, Daniel Kiper wrote:
> On Mon, Mar 16, 2020 at 05:41:29PM +0100, Daniel Kiper wrote:
> > On Wed, Mar 11, 2020 at 11:47:35AM +0100, Daniel Kiper wrote:
> > > On Tue, Mar 03, 2020 at 06:26:03PM +0100, Daniel Kiper wrote:
> > > > On Wed, Feb 19, 2020 at 04:01:38PM +0100, Daniel Kiper wrote:
> > > > > Hi all,
> > > > >
> > > > > As I told during my FOSDEM 2020 presentation we are preparing for
> > > > > GRUB 2.06 release. Tentative schedule is below:
> > > > >   - code freeze: 15th of March, 23:59:59 UTC; everything posted after
> > > > >     that date will not be considered as a release material,
> > > >
> > > > Just a kind reminder... Less than two weeks left...
> > >
> > > Less than a week left... This is final call...
> >
> > Freeze in force! No new features are accepted at this point!
> >
> > I will be reviewing all patches posted before the end of Sunday. All of
> > them will be considered for inclusion in the release. Additionally, all
> > features under active development and discussed on grub-devel still can
> > be considered for inclusion. However, if there is a substantial danger
> > of destabilizing the code or delaying the release I may reject any patch
> > at any point.
> >
> > I am especially interested in fixes and cleanups at this point...
> >
> > I am going to cut an RC in 2-4 weeks.
>
> Bad news is that we have delays... :-( Good news is that everything is going
> forward... :-) I merged next portion of patches yesterday. I am working
> on some fixes for issues which I found. I am also trying to work out
> the best solution for other bugs which are lingering here and there. So,
> please be patient... However, if you have any questions or suggestions
> just drop me a line...

Unfortunately there are still delays due to some unexpected things
happening... Though I am still ploughing through backlog. I have
recently posted a few fixes and cleanups required for rc1. Sadly there
are still a few issues which have to be fixed. I am working on them. So,
I hope that in the following weeks we will be able to cut rc1...

If you are waiting for my review please bear with me. I will get back to
you as soon as I can. Though I am mostly looking at important fixes in
first order right now.

Daniel


  reply	other threads:[~2020-05-29 12:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 15:01 GRUB 2.06 release Daniel Kiper
2020-02-20  8:46 ` John Paul Adrian Glaubitz
2020-02-25 13:15   ` John Paul Adrian Glaubitz
2020-02-28 12:46     ` Daniel Kiper
2020-02-28 18:26       ` Matt Turner
2020-02-29  1:40       ` Mike Gilbert
2020-03-03 17:26 ` Daniel Kiper
2020-03-03 17:33   ` John Paul Adrian Glaubitz
2020-03-05 13:34     ` Daniel Kiper
2020-03-04  4:39   ` Patrick Steinhardt
2020-03-05 13:50     ` Daniel Kiper
2020-03-07 16:29       ` Patrick Steinhardt
2020-03-11 10:47   ` Daniel Kiper
2020-03-16 16:41     ` Daniel Kiper
2020-04-22 10:24       ` Daniel Kiper
2020-05-29 12:07         ` Daniel Kiper [this message]
2020-07-29 17:46           ` Daniel Kiper
2020-10-19 16:30             ` Pete Batard
2020-10-20 19:00               ` Julian Andres Klode
2020-10-20 19:12                 ` Eli Schwartz
2020-10-20 20:05                   ` Julian Andres Klode
2020-10-20 20:33                     ` Eli Schwartz
2020-10-20 20:06                   ` Pete Batard
2020-10-20 20:03                 ` Pete Batard
2020-12-14 12:39             ` Daniel Kiper
2020-12-14 12:44               ` John Paul Adrian Glaubitz
2020-12-23 23:25               ` 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=20200529120729.4qa7bonugkkuannp@tomti.i.net-space.pl \
    --to=dkiper@net-space.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.