linux-kernel - Re: (Short?) merge window reminder

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.02.1105241147150.23692@asgard.lang.hm>
Date:	Tue, 24 May 2011 11:55:27 -0700 (PDT)
From:	david@...g.hm
To:	Matthias Schniedermeyer <ms@...d.de>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, DRI <dri-devel@...ts.freedesktop.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>
Subject: Re: (Short?) merge window reminder

On Tue, 24 May 2011, Matthias Schniedermeyer wrote:

> On 23.05.2011 13:33, Linus Torvalds wrote:
>> On Mon, May 23, 2011 at 12:20 PM, Ingo Molnar <mingo@...e.hu> wrote:
>>>
>>> I really hope there's also a voice that tells you to wait until .42 before
>>> cutting 3.0.0! :-)
>>
>> So I'm toying with 3.0 (and in that case, it really would be "3.0",
>> not "3.0.0" - the stable team would get the third digit rather than
>> the fourth one.
>
> What about strictly 3 part versions? Just add a .0.
>
> 3.0.0 - Release Kernel 3.0
> 3.0.1 - Stable 1
> 3.0.2 - Stable 2
> 3.1.0 - Release Kernel 3.1
> 3.1.1 - Stable 1
> ...
>
> Biggest problem is likely version phobics that get pimples when they see
> trailing zeros. ;-)

since there are always issues discovered with a new kernel is released 
(which is why the -stable kernels exist), being wary of .0 kernels is not 
neccessarily a bad thing.

I still think a date based approach would be the best.

since people are worried about not knowing when a final release will 
happen, base the date on when the merge window opened or closed (always 
known at the time of the first -rc kernel)

in the thread on lwn, people pointed out that the latest 2.6.32 kernel 
would still be a 2009.12.X which doesn't reflect the fact that it was 
released this month. My suggestion for that is to make the X be the number 
of months (or years.months if you don't like large month values) between 
the merge window and the release of the -stable release. This would lead 
to a small problem when there are multiple -stable releases in a month, 
but since that doesn't last very long I don't see a real problem with just 
incramenting the month into the future in those cases.

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