linux-kernel - Re: Linux 3.12 released .. and 4.0 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]

Date:	Tue, 05 Nov 2013 06:08:12 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	Jan Engelhardt <jengelh@...i.de>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.12 released .. and 4.0 plans?

Am 04.11.2013 22:46, schrieb Jan Engelhardt:
> 
> On Monday 2013-11-04 01:10, Linus Torvalds wrote:
>>
>> Onto a totally different topic: we're getting to release numbers where
>> I have to take off my socks to count that high again. I'm ok with
>> 3.<low teens> [...] [4.0 "ok, after 3.19 (or whatever),"]
> 
> What would you do when the major number becomes such an unpleasant
> highteen number? (That will be in ~64 years if you wrap after x.19.)

Changing the counting base and going hex would offer some more years. So
after 9.19 he could switch to a.0 instead of 10.0. Or just call it then
LinuxNG and start with 1.0 again.

But to add something serious to the discussion too, I don't see a reason
why to make a bugfix-only version.

There should be no need to spend a version number for a bugfix only time.

E.g. just insert a bugfix-only time (handled like times at -rc7) before
a merge window for a new version. That would give people the possibility
to get their bugfix-patches into mainline in order to get them into the
stable series without the need to spend a version number.

Regards,

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