linux-kernel - Re: 2.6.19 -mm merge plans

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: <45123307.8090809@garzik.org>
Date:	Thu, 21 Sep 2006 02:36:55 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andrew Morton <akpm@...l.org>
CC:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: 2.6.19 -mm merge plans

Andrew Morton wrote:
> If you think that shortening the release cycle will cause people to be more
> disciplined in their changes, to spend less time going berzerk and to spend
> more time working with our users and testers on known bugs then I'm all
> ears.

Honestly, I do think it would be positive.  It would shorten the 
feedback loop, and get more changes out to testers.

It would also decrease the pressure of the 60+ trees trying to get 
everything in, because they know the next release is 3-4 months away. 
It would be _much_ easier to say "break the generic device stuff in 
2.6.20 not 2.6.19, please" if we knew 2.6.20 wasn't going to be a 2007 
release.

	Jeff

-
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/