From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: update on the planning
Date: Fri, 5 May 2006 20:07:24 +0200 [thread overview]
Message-ID: <200605052007.24183.okuji@enbug.org> (raw)
In-Reply-To: <87ejz8n14w.fsf@xs4all.nl>
Hi Marco,
On Friday 05 May 2006 13:48, Marco Gerards wrote:
> Eventually this has to happen if we want people to use GRUB 2. So I
> agree with that. It's to soon for me to determine if November is
> reasonable or not. But if we want to pick a date, this date is as
> good as any. At least it is not too soon or late for my feeling.
:)
> For me it will mean that scripting should be finished soon. At least
> the rough work and functionality. Same for networking interfaces, the
> GUI layering splitup and we have to determine before that what should
> be a command and what should go into a variable. But let's not
> discuss this right here, right now.
Please do not harass yourself with this. ;)
I mean that GRUB 2 should not introduce incompatibility after 1.96 _against
GRUB 2_ rather than GRUB Legacy. So as long as you are careful, you can add
more features later. In fact, I have added a lot of new features into GRUB
Legacy without losing any backward compatibility. Since GRUB 2 has a cleaner
design, I expect that this would be even easier.
The goal is that the user can start to use GRUB 2 while not scared of a
breakage due to incompatible changes. This also eases the documentation
significantly. In GRUB Legacy, this way worked very well. I was even
surprised that it was not necessary to release a public version at all. :p
As you said, it is necessary to make this kind of decision at a point,
although it has been fun that we don't have to care about incompatibility for
these 3 years. Yet, we still have 6 months in my plan, so you don't have to
feel threatened.
Okuji
prev parent reply other threads:[~2006-05-05 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 20:34 update on the planning Yoshinori K. Okuji
2006-05-05 11:48 ` Marco Gerards
2006-05-05 18:07 ` Yoshinori K. Okuji [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=200605052007.24183.okuji@enbug.org \
--to=okuji@enbug.org \
--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.