Re: From 2.4 to 2.6 to 2.7?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Alberto Gonzalez
Date: Tuesday, July 15, 2008 - 6:18 am

On Tuesday 15 July 2008, Kasper Sandberg wrote:

Sorry for entering a discussion from a project I'm just a user of, but I was 
thinking... I do see smallish problems with current scheme:

- First two numbers never change (2.6), so they're mostly useless.
- Third number gets too big (currently 26, and growing)
- Stable releases are already a fourth number (2.6.25.11. Unconfortable).

So a possible solution that would not break completely with historical numbers 
could be:

- Since you're aproaching 2.6.30 (around mid 2009), why not agree tu turn that 
into a 3.0 release? Peope have been expecting a version 3 of the kernel for a 
long time now... It might give the (false) impression that it's an all new 
release, but it would be explained that it's just a normal one. However, I 
also think that by that time, the last "problem" with Linux will be solved, 
i.e, the graphics thing. With the changes in DRM/DRI starting to appear in 
2.6.27 (maybe), they will stabilize through .28 and .29, making .30 a good 
release to declare the Linux kernel "completely mature", without any weak 
spot (so to say) and turn it into 3.0 release (the Free drivers for ATI and 
even NVIDIA will hopefully be mature by then too, as might be Gallium3D, 
VA-API, GEM/TTM, etc... )

- From there, how to proceed? Instead of making the same mistake again of 
having a useless middle number, each release would increment by a 10th. That 
is, instead of 3.0.1, 3.0.2, etc... just 3.1, 3.2, 3.3, etc... Then the stable 
releases would be 3.1.1, 3.1.2, etc... (no longer a 4 series of numbers). And 
after 3.9, we would have 4.0 to avoid having again a too bit number (3.26, 
etc...). Roughly, you release 5 kernels per year, so that would give enough 
time until you hit a high number (it will increment by one every two years). 
For example, it would take 20 years from 2009 until you hit version 13.0. 
Twenty years is a decent amount of time in kernel development. And well, even 
13 is not _that_ big anyway. You can push this numbering up to version 20 if 
necessary and that would give another 14 extra years. By then (year 2043) I'm 
sure that someone will have come up with a smart way of rearranging the 
numbering once more :-)

Regards.

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
From 2.4 to 2.6 to 2.7?, Stoyan Gaydarov, (Mon Jul 14, 7:10 pm)
Re: From 2.4 to 2.6 to 2.7?, Linus Torvalds, (Mon Jul 14, 7:22 pm)
Re: From 2.4 to 2.6 to 2.7?, Stoyan Gaydarov, (Mon Jul 14, 7:31 pm)
Re: From 2.4 to 2.6 to 2.7?, Linus Torvalds, (Mon Jul 14, 7:47 pm)
Re: From 2.4 to 2.6 to 2.7?, david, (Mon Jul 14, 8:55 pm)
Re: From 2.4 to 2.6 to 2.7?, Willy Tarreau, (Mon Jul 14, 10:31 pm)
Re: From 2.4 to 2.6 to 2.7?, Rafael C. de Almeida, (Mon Jul 14, 11:40 pm)
Re: From 2.4 to 2.6 to 2.7?, Stoyan Gaydarov, (Tue Jul 15, 12:23 am)
Re: From 2.4 to 2.6 to 2.7?, Jan Engelhardt, (Tue Jul 15, 12:49 am)
Re: From 2.4 to 2.6 to 2.7?, Bernd Petrovitsch, (Tue Jul 15, 1:29 am)
Re: From 2.4 to 2.6 to 2.7?, Andi Kleen, (Tue Jul 15, 3:10 am)
Re: From 2.4 to 2.6 to 2.7?, Jan Engelhardt, (Tue Jul 15, 4:31 am)
Re: From 2.4 to 2.6 to 2.7?, Alan Cox, (Tue Jul 15, 5:38 am)
Re: From 2.4 to 2.6 to 2.7?, Kasper Sandberg, (Tue Jul 15, 5:41 am)
Re: From 2.4 to 2.6 to 2.7?, Alberto Gonzalez, (Tue Jul 15, 6:18 am)
Re: From 2.4 to 2.6 to 2.7?, Byron Stanoszek, (Tue Jul 15, 7:07 am)
Re: From 2.4 to 2.6 to 2.7?, Cyrill Gorcunov, (Tue Jul 15, 7:24 am)
Re: From 2.4 to 2.6 to 2.7?, Linus Torvalds, (Tue Jul 15, 8:20 am)
Re: From 2.4 to 2.6 to 2.7?, Tobias Brox, (Tue Jul 15, 9:36 am)
Re: From 2.4 to 2.6 to 2.7?, H. Peter Anvin, (Tue Jul 15, 11:04 am)
Re: From 2.4 to 2.6 to 2.7?, Charles grey wolf Banas, (Tue Jul 15, 11:06 am)
Re: From 2.4 to 2.6 to 2.7?, Adrian Bunk, (Tue Jul 15, 1:43 pm)
Re: From 2.4 to 2.6 to 2.7?, Rene Herman, (Tue Jul 15, 9:22 pm)
Re: From 2.4 to 2.6 to 2.7?, Rafael C. de Almeida, (Tue Jul 15, 11:55 pm)
Re: From 2.4 to 2.6 to 2.7?, Rene Herman, (Wed Jul 16, 12:17 am)
Re: From 2.4 to 2.6 to 2.7?, Rene Herman, (Wed Jul 16, 12:30 am)
Re: From 2.4 to 2.6 to 2.7?, Jan Engelhardt, (Wed Jul 16, 12:53 am)
Re: From 2.4 to 2.6 to 2.7?, Rene Herman, (Wed Jul 16, 12:57 am)
Re: From 2.4 to 2.6 to 2.7?, Peter T. Breuer, (Wed Jul 16, 2:34 am)
Re: From 2.4 to 2.6 to 2.7?, Lennart Sorensen, (Wed Jul 16, 2:11 pm)
Re: From 2.4 to 2.6 to 2.7?, Lennart Sorensen, (Wed Jul 16, 2:14 pm)
Re: From 2.4 to 2.6 to 2.7?, Alex Chiang, (Wed Jul 16, 5:03 pm)
Re: From 2.4 to 2.6 to 2.7?, Lennart Sorensen, (Thu Jul 17, 5:38 am)
Re: From 2.4 to 2.6 to 2.7?, Jan Engelhardt, (Thu Jul 17, 10:25 am)
Re: From 2.4 to 2.6 to 2.7?, Craig Milo Rogers, (Thu Jul 17, 12:56 pm)
Re: From 2.4 to 2.6 to 2.7?, Alex Chiang, (Thu Jul 17, 1:02 pm)
Re: From 2.4 to 2.6 to 2.7?, Jan Engelhardt, (Thu Jul 17, 1:21 pm)
Re: From 2.4 to 2.6 to 2.7?, Adrian Bunk, (Thu Jul 17, 3:16 pm)
Re: From 2.4 to 2.6 to 2.7?, Craig Milo Rogers, (Sat Jul 19, 1:00 am)
Re: From 2.4 to 2.6 to 2.7?, Rene Herman, (Sat Jul 19, 1:52 am)
Re: From 2.4 to 2.6 to 2.7?, Peter T. Breuer, (Sat Jul 19, 12:30 pm)
Re: From 2.4 to 2.6 to 2.7?, Craig Milo Rogers, (Sat Jul 19, 1:49 pm)
Re: From 2.4 to 2.6 to 2.7?, david, (Sat Jul 19, 1:56 pm)
Re: From 2.4 to 2.6 to 2.7?, Craig Milo Rogers, (Sat Jul 19, 2:16 pm)
Re: From 2.4 to 2.6 to 2.7?, Jan Engelhardt, (Sat Jul 19, 2:56 pm)
Re: From 2.4 to 2.6 to 2.7?, Peter T. Breuer, (Sat Jul 19, 4:10 pm)
Re: From 2.4 to 2.6 to 2.7?, Rene Herman, (Sun Jul 20, 1:34 am)
Re: From 2.4 to 2.6 to 2.7?, Stefanos Harhalakis, (Sun Jul 20, 7:53 am)