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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4DDD0E5F.5080105@panasas.com>
Date:	Wed, 25 May 2011 17:12:47 +0300
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	Alexey Zaytsev <alexey.zaytsev@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	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 05/23/2011 11:52 PM, Alexey Zaytsev wrote:
> On Tue, May 24, 2011 at 00:33, Linus Torvalds
> <torvalds@...ux-foundation.org> 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.
>>
>> But no, it wouldn't be for 42. Despite THHGTTG, I think "40" is a
>> fairly nice round number.
>>
>> There's also the timing issue - since we no longer do version numbers
>> based on features, but based on time, just saying "we're about to
>> start the third decade" works as well as any other excuse.
>>
>> But we'll see.
> 
> Maybe, 2011.x, or 11.x, x increasing for every merge window started this year?
> This would better reflect the steady nature of the releases, but would
> certainly break a lot of scripts. ;)

My $0.017 on this. Clearly current process is time based. People have said.

* Keep Three digit numbers to retain script compatibility
* Make it clear from the version when it was released.
* Linus said 3 as for 3rd decade
* Nice single increment number progression
* Please make it look like a nice version number sys-admins will feel
  at home with

So if you combine all the above:

D. Y. N
D - Is the decade since birth (1991 not 1990)
Y - is the year in the decade so you have 3.1.x, 3.2.x, .. 3.10.x, 4.1.X and so on
    Nice incremental number.
N - The Linus release of this Year. So this 3rd one goes up to 4 most probably.

Linus always likes, and feels very poetic about the Christmas version release.
He hates it when once it slipped into the next year. So now he gets to increment
the second digit as a bonus.

The 2nd digit gets to start on a *one*, never zero and goes up to *10*, to symbolize
the 1991 birth. And we never have .zero quality, right?

The first Digit gets incremented on decade from 1991 so on 2011 and not 2010

So here you have it, who said we need to compromise?

Free life
Boaz
 
--
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/