All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Subject: update on the planning
Date: Thu, 4 May 2006 22:34:53 +0200	[thread overview]
Message-ID: <200605042234.53201.okuji@enbug.org> (raw)

I have updated the planning:

http://grub.enbug.org/ReleasePlanning

I'm planning to release next version in one month. This time, I myself will do 
this instead of Marco.

As in the plan, I would like to stabilize GRUB 2 at 1.96. This means that we 
will not introduce any incompatibility after November (from the users' point 
of view). Currently, I'm going to apply the same policy as GRUB 1.90-1.96, 
that is, we still accept new features but not incompatible changes. So, if 
you want to change anything, you must propose (and implement) it before 
November.

Do you agree with this policy? This is just a plan, so I can change it, if you 
don't like.

After 1.96, my plan is not clear yet. Now is too early to discuss this.

Okuji



             reply	other threads:[~2006-05-04 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 20:34 Yoshinori K. Okuji [this message]
2006-05-05 11:48 ` update on the planning Marco Gerards
2006-05-05 18:07   ` Yoshinori K. Okuji

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=200605042234.53201.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.