From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>,
Colin Watson <cjwatson@debian.org>,
Peter Jones <pjones@redhat.com>,
Andrey Borzenkov <arvidjaar@gmail.com>
Subject: Re: Bugs and tasks for 2.02[~rc1]
Date: Tue, 12 Apr 2016 12:53:49 -0500 [thread overview]
Message-ID: <570D362D.1020505@gmail.com> (raw)
In-Reply-To: <CAEaD8JPQdPkLWQjNpp2YX3KZJiFuA0bGKkNz7dzhVFHSYg068A@mail.gmail.com>
Vladimir 'phcoder' Serbinenko wrote:
> Hello, all. I went through the list of bugs and created a shortlist of bugs
> that need to be looked at for 2.02. I have marked them with plan_release_id
> set to 2.02.
[snip]
> I would like to come up with a complete list of 2.02 blockers in one week
> time, so that we can have a reasonable timeline
Is there an updated list of blockers? Is there a time estimate for the
2.02 release?
-- Bruce
next prev parent reply other threads:[~2016-04-12 17:54 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 15:01 Bugs and tasks for 2.02[~rc1] Vladimir 'phcoder' Serbinenko
2016-03-02 22:24 ` Daniel Kiper
2016-03-09 10:49 ` Daniel Kiper
[not found] ` <20160309144557.GA19753@char.us.oracle.com>
2016-03-09 14:51 ` Vladimir 'phcoder' Serbinenko
2016-03-09 20:05 ` Daniel Kiper
2016-03-04 20:06 ` Peter Jones
2016-03-05 8:38 ` Andrei Borzenkov
2016-03-07 19:00 ` Peter Jones
2016-03-07 19:57 ` Vladimir 'phcoder' Serbinenko
2016-03-07 20:33 ` Andrei Borzenkov
2016-03-07 20:40 ` Vladimir 'phcoder' Serbinenko
2016-03-07 20:57 ` Andrei Borzenkov
2016-03-07 21:03 ` Vladimir 'phcoder' Serbinenko
2016-03-07 21:20 ` Peter Jones
2016-03-07 21:29 ` Andrei Borzenkov
2016-03-07 22:01 ` Peter Jones
2016-03-07 22:07 ` Vladimir 'phcoder' Serbinenko
2016-03-08 4:16 ` Michael Chang
2016-03-08 3:40 ` Michael Chang
2016-03-08 4:57 ` Andrei Borzenkov
2016-03-09 15:18 ` Matt Fleming
2016-03-09 20:15 ` Linux loader EFI handover (was: Bugs and tasks for 2.02[~rc1]) Andrei Borzenkov
2016-03-10 14:21 ` Matt Fleming
2016-03-11 17:46 ` Linux loader EFI handover Andrei Borzenkov
2016-03-07 21:42 ` Bugs and tasks for 2.02[~rc1] Matt Fleming
2016-03-11 15:51 ` Vladimir 'phcoder' Serbinenko
2016-03-14 15:17 ` Matt Fleming
2016-03-15 17:38 ` Vladimir 'phcoder' Serbinenko
2016-03-22 17:54 ` Peter Jones
2016-03-07 21:14 ` Peter Jones
2016-03-07 21:50 ` Vladimir 'phcoder' Serbinenko
2016-03-07 21:10 ` Peter Jones
2016-03-11 18:01 ` Andrei Borzenkov
2016-03-07 21:03 ` Peter Jones
2016-03-07 21:08 ` Andrei Borzenkov
2016-03-07 21:26 ` Peter Jones
2016-03-07 21:08 ` Vladimir 'phcoder' Serbinenko
2016-03-08 17:57 ` Andrei Borzenkov
2016-03-08 21:47 ` Peter Jones
2016-03-11 18:38 ` Andrei Borzenkov
2016-03-09 6:38 ` Olaf Hering
2016-03-09 7:54 ` Michael Chang
2016-03-09 8:13 ` Andrei Borzenkov
2016-03-11 16:04 ` Vladimir 'phcoder' Serbinenko
2016-04-13 8:49 ` Olaf Hering
2016-03-13 6:30 ` Andrei Borzenkov
2016-03-22 18:48 ` Vladimir 'phcoder' Serbinenko
2016-03-22 19:51 ` Andrei Borzenkov
2016-04-18 4:18 ` Vladimir 'phcoder' Serbinenko
[not found] ` <20160328145903.GF17944@char.us.oracle.com>
2016-04-12 16:44 ` Konrad Rzeszutek Wilk
2016-04-18 4:20 ` Vladimir 'phcoder' Serbinenko
2016-04-12 17:53 ` Bruce Dubbs [this message]
2016-04-18 4:20 ` Vladimir 'phcoder' Serbinenko
-- strict thread matches above, loose matches on Subject: below --
2016-03-03 14:47 Juergen Gross
2016-03-09 10:52 ` Daniel Kiper
2016-03-11 15:47 ` Vladimir 'phcoder' Serbinenko
2016-03-11 15:57 ` Juergen Gross
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=570D362D.1020505@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=arvidjaar@gmail.com \
--cc=cjwatson@debian.org \
--cc=grub-devel@gnu.org \
--cc=pjones@redhat.com \
/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.