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: <4512DB05.2090604@garzik.org>
Date:	Thu, 21 Sep 2006 14:33:41 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Linus Torvalds <torvalds@...l.org>
CC:	Andrew Morton <akpm@...l.org>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19 -mm merge plans

Linus Torvalds wrote:
> One of the things that I think the current model has excelled at is how it 
> really changed peoples behaviour, simply because they knew and understood 
> the rules.
> 
> I think the "big merges in the first two weeks, and a -rc1 after, and no 
> new code after that" rule has been working because it brought everybody in 
> on the same page. 

I definitely agree with all that.

I simply argue that, the more time that passes between releases, the 
MORE BUGS that appear in the next release.

After -rc1, you reach a point of diminishing returns where users don't 
re-test Release Candidates, developers move on to new code rather than 
fix bugs, and we all move into a limbo where 2.6.X-rcY doesn't see much 
activity, but the huge "merge snowball" in -mm builds and builds and builds.

As an aside, if a release is getting held up by some key bugs or 
regressions, I think it's more than fair for Andrew to loudly shame said 
developers into action.  "The following nincompoops are holding up the 
release:  Jeff Garzik [bug #1222, #3391], Greg KH [bug #9987, #4418], ..."

	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/