mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Snitzer" <snitzer@gmail.com>
To: "Tarkan Erimer" <tarkan@netone.net.tr>
Cc: "Pekka Enberg" <penberg@cs.helsinki.fi>,
	"Arjan van de Ven" <arjan@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion About Kernel Releases
Date: Wed, 21 May 2008 10:32:25 -0400	[thread overview]
Message-ID: <170fa0d20805210732s24f2c188i75ab2ab2dab5aeb5@mail.gmail.com> (raw)
In-Reply-To: <48342B19.9040407@netone.net.tr>

On Wed, May 21, 2008 at 10:00 AM, Tarkan Erimer <tarkan@netone.net.tr> wrote:
> Pekka Enberg wrote:
>
> > On Wed, 21 May 2008 16:08:37 +0300, Tarkan Erimer <tarkan@netone.net.tr>
> wrote:
> >
> >
> > >
> > > > After long discussions about kernel release methodology, an idea has
> > > > came to ( Any comments welcomed :-) ) my mind :
> > > >
> > > >
> > >
> >
> > On Wed, May 21, 2008 at 4:38 PM, Arjan van de Ven <arjan@infradead.org>
> wrote:
> >
> >
> > > what would you want to accomplish with your idea?
> > >
> > >
> >
> > And how is it different from what we do now, modulo the -test1 postfix
> > to the name?
> >
> >
>
>  Please see my reply to Arjan's post.

I think you're missing Arjan and Pekka's point: your proposal doesn't
_really_ offer any change to the current procedure.  It might make you
feel more warm and fuzzy but in practice:
1) Linus would still release a kernel (be it to -testX or "final")
when he and others feel it is time
2) The stable team will track fixes and release stable kernels as needed

The only thing that is different in your approach is the "final"
release would theoretically be more well tested.  Unfortunately that
is not a valid assumption because the wider Linux audience likely
won't embrace the latest kernel until it is "final" anyway.  This
delayed uptake can/will result in early stable fixes.

Again, no real change... we know that the "final" release that Linus
makes _could_ have some minor oversight that will be fixed fairly
quickly by the stable team.

Mike

  reply	other threads:[~2008-05-21 14:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 13:08 Tarkan Erimer
2008-05-21 13:38 ` Arjan van de Ven
2008-05-21 13:48   ` Pekka Enberg
2008-05-21 14:00     ` Tarkan Erimer
2008-05-21 14:32       ` Mike Snitzer [this message]
2008-05-21 15:15         ` Tarkan Erimer
2008-05-21 15:26           ` Pekka Enberg
2008-05-24  3:11             ` Enrico Weigelt
2008-05-21 13:59   ` Tarkan Erimer
2008-05-21 14:28     ` Arjan van de Ven
2008-05-21 14:50       ` Tarkan Erimer
2008-05-21 15:12         ` Arjan van de Ven
2008-05-21 17:31     ` Chris Wright
2008-05-22  6:46       ` Tarkan Erimer
2008-05-21 19:55     ` Rik van Riel
2008-05-21 14:37 ` Oliver Pinter

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=170fa0d20805210732s24f2c188i75ab2ab2dab5aeb5@mail.gmail.com \
    --to=snitzer@gmail.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=tarkan@netone.net.tr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®