All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Building a steady release cycle
Date: Mon, 05 Jan 2009 20:07:10 +0200	[thread overview]
Message-ID: <49624C4E.1030209@nic.fi> (raw)
In-Reply-To: <9f50a7a00901041945j566980c2t3fcc0390a092e24d@mail.gmail.com>

Jerone Young wrote:
> Hey guys,
> 
>         I wanted to start up a discussion on building a steady release
> cycle. Many distros are now looking for some stability from Grub 2 as they
> are looking to include it in future releases. I was recently at the Ubuntu
> Developer Summit in December discussing the possibility of including grub 2
> in future releases. One of the big concerns was that there was not a steady
> release policy working up to 2.0.

I think it would be best to organize a release team which would then
plan and explode release to tasks so people could grab one and develop
them. Of course there should be some "backup" people that features
really do get developed.

Perhaps bi-weekly status checks would be a good idea to keep up with
status of every feature.

I can volunteer to be part of such team if decided to be started.

Also this work should be visible so it would be easy for others to tag
alone and help to develop missing features and to submit patches.




  parent reply	other threads:[~2009-01-05 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05  3:45 Building a steady release cycle Jerone Young
2009-01-05  3:55 ` Jerone Young
2009-02-07 20:30   ` Robert Millan
2009-01-05 18:07 ` Vesa Jääskeläinen [this message]
2009-01-16  7:20   ` shirish

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=49624C4E.1030209@nic.fi \
    --to=chaac@nic.fi \
    --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.