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: <45133666.2060601@tmr.com>
Date:	Thu, 21 Sep 2006 21:03:34 -0400
From:	Bill Davidsen <davidsen@....com>
To:	Jeff Garzik <jeff@...zik.org>
CC:	Linus Torvalds <torvalds@...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

Jeff Garzik wrote:
> Bill Davidsen wrote:
>> I think it would help if you went back to using meaningful names for 
>> releases, because 2.6.19-test1 is pretty clearly a test release even 
>> to people who can't figure out if a number is odd or even. Then after 
>> people stop reporting show stoppers, change to rc numbers, where rc 
>> versions are actually candidates for release without known major bugs.
> 
> 
> Actually, considering our group of developers, I think "-rc" has been 
> remarkably successful at staying on the "bug fixes only" theme.
> 
Perhaps I misread what Linus said, the issue I was suggesting be 
addressed was one of clarity to the testers, not the developers. The 
releases identified as test would be for evaluation, while the ones 
identified as rc would really be candidates with no "fix before next 
version" bugs known. I  would think that between test releases some bugs 
could be fixed, but new features could be added. That would encourage 
more active testing without overly slowing the development process.

Having used that for a long time for 2.2 and 2.4 I think there's quite a 
track record of that nomenclature being clear to the users.

-- 
Bill Davidsen <davidsen@....com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
-
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/