From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Should the website still say that GRUB 2 is currently under development?
Date: Fri, 31 Jul 2009 18:19:58 +0200 [thread overview]
Message-ID: <20090731161958.GJ14675@thorin> (raw)
In-Reply-To: <1248968735.27471.40.camel@mj>
On Thu, Jul 30, 2009 at 11:45:35AM -0400, Pavel Roskin wrote:
> On Thu, 2009-07-30 at 15:05 +0200, adrian15 wrote:
> > Felix Zielcke escribió:
> > > I think the currently under development part can be now removed.
> > > Or would it be better to wait for the 1.97 release? (which hopefully
> > > comes before December)
> > That would be nice because Debian freezes at December.
>
> I don't see anything wrong with being "under development". I hope that
> GRUB 2 will be under development even after the 1.97. I don't see how
> Debian can have any problem with that.
It depends. If we say GRUB 2 is "under development" but we don't say anything
about GRUB Legacy, people might think GRUB 2 is not ready.
I agree with Pavel, saying GRUB 2 is under development doesn't fail to the
truth, but then again there are many ways of saying the truth. I think we
should make the website give a clear message that:
a) GRUB Legacy is obsolete and we don't longer support it
b) GRUB 2 is more mature than GRUB Legacy
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-07-31 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 12:06 Should the website still say that GRUB 2 is currently under development? Felix Zielcke
2009-07-30 13:05 ` adrian15
2009-07-30 15:45 ` Pavel Roskin
2009-07-30 16:18 ` Felix Zielcke
2009-07-31 10:44 ` Colin Watson
2009-07-31 16:19 ` Robert Millan [this message]
2009-08-10 13:25 ` Felix Zielcke
2009-08-10 15:28 ` Robert Millan
2009-10-25 18:21 ` Felix Zielcke
2009-10-26 0:33 ` Felix Zielcke
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=20090731161958.GJ14675@thorin \
--to=rmh@aybabtu.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 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.