linux-kernel - Re: Suggestion About Kernel Releases

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <170fa0d20805210732s24f2c188i75ab2ab2dab5aeb5@mail.gmail.com>
Date:	Wed, 21 May 2008 10:32:25 -0400
From:	"Mike Snitzer" <snitzer@...il.com>
To:	"Tarkan Erimer" <tarkan@...one.net.tr>
Cc:	"Pekka Enberg" <penberg@...helsinki.fi>,
	"Arjan van de Ven" <arjan@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Suggestion About Kernel Releases

On Wed, May 21, 2008 at 10:00 AM, Tarkan Erimer <tarkan@...one.net.tr> wrote:
> Pekka Enberg wrote:
>
> > On Wed, 21 May 2008 16:08:37 +0300, Tarkan Erimer <tarkan@...one.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@...radead.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/