From: Daniel Kiper <dkiper@net-space.pl>
To: grub-devel@gnu.org
Subject: GRUB 2.06 release
Date: Wed, 19 Feb 2020 16:01:38 +0100 [thread overview]
Message-ID: <20200219150138.sq76t2oyed6xa62y@tomti.i.net-space.pl> (raw)
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,
- release: taking into account last experience I think that it will
happen no later than June; hopefully earlier; exact date depends
on number of bugs found, etc.
So, please plan accordingly...
If you have any questions, suggestions, etc. drop me a line.
Daniel
next reply other threads:[~2020-02-19 15:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:01 Daniel Kiper [this message]
2020-02-20 8:46 ` GRUB 2.06 release 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
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=20200219150138.sq76t2oyed6xa62y@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.