From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB release schedule?
Date: Sat, 22 Aug 2015 08:16:26 +0300 [thread overview]
Message-ID: <55D805AA.1070805@gmail.com> (raw)
In-Reply-To: <20150821184157.GB1948@l.oracle.com>
21.08.2015 21:41, Konrad Rzeszutek Wilk пишет:
>
> Lets start with a list of priorities:
> - What are the most important platforms after x86?
I suppose distribution-wise they are ARM and PPC. This means 5 different
GRUB builds. MIPS seems to be still in use, at least there are patches
and bug reports.
> - What are the most important tests that MUST PASS all the time?
All of them actually. There is one test that unfortunately is bound to
fail unless built in controlled environment.
> - Which ones have been FAILing for years?
>
Hard to know, there are no published results.
next prev parent reply other threads:[~2015-08-22 5:16 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
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 [this message]
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=55D805AA.1070805@gmail.com \
--to=arvidjaar@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).