All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: release planning
Date: Sun, 17 Jul 2005 22:23:38 +0200	[thread overview]
Message-ID: <87d5phdvw5.fsf@student.han.nl> (raw)
In-Reply-To: <200507171739.31922.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sun, 17 Jul 2005 17:39:31 +0200")

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

Hi Okuji,

> If there is no objection, I'd like to release the first version of GRUB 2 for 
> developers at the beginning of August, whatever status it is in. At the 
> moment, I'm devoting myself into bugfixes and incorporation of workarounds 
> from GRUB Legacy. I'm also going to implement a simple installer for 
> GNU/Linux within this month.

It's very nice that you are working this hard now.  It is really nice
to see someone is working on the PC specific code again.  I am looking
forwards to the release.  It would be nice if we could get a
kerneltrap article, it could attract more developers. :)

> After that, I'd like to keep releasing new versions constantly. Hopefully, one 
> per two or three months. The version numbers will be 1.9x, until we make GRUB 
> 2 stable enough on PC.

Ok, fine for me.

> Currently, I believe that PC support is the priority, because people just 
> stick to GRUB Legacy, and do not take part in GRUB 2. I won't push my opinion 
> to others, but I wish others attach importance to the PC support and/or the 
> generic part as well.

Right.  I assume things remain like they are?  For me PC support is
very important, although I work more on PPC support.  Please tell us
when you think there is a problem for the PC support caused by another
port.

> As I guess contributors in GRUB do not like to be specified what they should 
> do, I'm not going to specify milestones for release management.

No, that would not be wise.  But having a good prioritized TODO list
is important and people pick up the TODO items quite well.

Thanks,
Marco




  reply	other threads:[~2005-07-17 20:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17 15:39 release planning Yoshinori K. Okuji
2005-07-17 20:23 ` Marco Gerards [this message]
2005-07-17 20:30   ` Gregg C Levine
2005-07-17 21:13     ` Marco Gerards
2005-07-17 21:39       ` Gregg C Levine
2005-07-18  9:07         ` Yoshinori K. Okuji
2005-07-18 20:01           ` Gregg C Levine
2005-07-18 15:03   ` GRUB history Hollis Blanchard
2005-07-19 10:32     ` Marco Gerards
2005-07-18  7:28 ` release planning Tobias Wollgam
2005-07-18 15:01 ` Hollis Blanchard
2005-07-18 15:30   ` James Buchanan
2005-07-18 16:32     ` Marco Gerards
2005-07-18 20:33     ` 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=87d5phdvw5.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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.