From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: ReleasePlanning page on wiki
Date: Tue, 02 Sep 2008 11:42:46 +0200 [thread overview]
Message-ID: <1220348566.4101.14.camel@fz.local> (raw)
In-Reply-To: <200807201113.53697.okuji@enbug.org>
Am Sonntag, den 20.07.2008, 11:13 +0200 schrieb Yoshinori K. Okuji:
Hello Okuji,
> I will find a way to keep it up-to-date.
>
I hope that you still try to find a way to update that page at least
once now.
Honourly I'd like to just remove it.
Before I started to constribute with grub2, a bit more then 2 months
ago, I practically only know that there is a thing called grub2.
But now I've learned much about it's current state, I even try hard on
IRC to get people to use it instead of grub-legacy.
The current state of this page isn't making a good view of grub2.
1.96 was actually released 2008 not 2006 as the page says.
and according to that page grub2 is still not as good as grub-legacy,
but I personally think it is except some missing features and
documentation.
But just for the bugs it is in my opion.
`Each release should be made regularly, regardless of the status.
Possibly every 2-3 months.'
I don't have a problem at all if you don't do this but it's currently
not at all true.
Okuji please try to find a bit time to update that page at least once.
The next Debian stable release named `lenny' will ship with grub2 and
hopefully for the stable release after it named `squeeze' grub2 will be
the default instead of grub-legacy.
grub2 is really in a good shape now but if people look at that page I
doubt they get it.
--
Felix Zielcke
prev parent reply other threads:[~2008-09-02 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 21:18 ReleasePlanning page on wiki Felix Zielcke
2008-07-20 9:13 ` Yoshinori K. Okuji
2008-07-20 10:00 ` Felix Zielcke
2008-09-02 9:42 ` Felix Zielcke [this message]
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=1220348566.4101.14.camel@fz.local \
--to=fzielcke@z-51.de \
--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.