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: <20080521155559.11f880d1@bree.surriel.com>
Date:	Wed, 21 May 2008 15:55:59 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Tarkan Erimer <tarkan@...one.net.tr>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Suggestion About Kernel Releases

On Wed, 21 May 2008 16:59:56 +0300
Tarkan Erimer <tarkan@...one.net.tr> wrote:

> Even, Linus can releases new kernels more quickly. Because, testing
> purpose should be handled by someone else like Chris did for 2.6.x.y.

If Linus were to go straight from merge window to merge window,
with stabilization happening in parallel, then there would be
no stable basis at the start of each merge window and bugs can
just pile up.

Speeding things up could lead to the same kind of code quality
issues we used to have in the 1.3, 2.1, 2.3 and 2.5 kernel series.

Slowing down regularly is good, not bad.

-- 
All rights reversed.
--
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/