Skip to contentSkip to conversation

On Linux numbering scheme

DISCUSSION Artem S. Tashkinov 4 participants 5 messages Oct 22, 2010 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 5600814.270321287742009359.JavaMail.root@mail-zbox20.bo3.lycos.com

#1 lore raw

I don't suggest changing it completely per se, I only propose to make
it a bit saner and more comprehensible.

Right now the end user given a kernel release number won't be able to say if his kernel is recent enough or not. The new numbering scheme makes it easy to understand when a particular kernel was released and makes it quite obvious to see how old the running kernel is.

What can you say about kernel 2.6.32? Almost nothing.

What can you say about kernel 3.11.3? - it is the third release of Linux in 2011.

Best wishes,

Artem

Quoted 36 lines · ----- "Athanasius
Quoted 3 lines · Al Viro
Quoted 1 line · kevin granade

Any particular reason not to continue the date-oriented format

and

Quoted 1 line
Quoted 1 line

have the third number be the numerical representation of the

month

Quoted 1 line
Quoted 1 line

rather than an incrementing numbering of the releases? It would

still

Quoted 1 line
Quoted 1 line

be monotonically increasing, which is the only requirement,

right?

Quoted 2 lines

Why do we need to change it, anyway?

/agree

For the most part it's only distribution maintainers that see or
care
about the kernel version number anyway. Anyone else knows what they're
getting into if they compile a kernel themselves, and otherwise is more
likely to say they're using "Linux 10.10" right now ....

Having said that I had a lovely suggestion in the last round on
this
topic which would allow you to know when a kernel was released just from
its version number :).

Signature · 5 lines
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
	   "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole -
ME
#2 lore raw
Quoted 4 lines · Artem S. Tashkinov

What can you say about kernel 2.6.32? Almost nothing.

What can you say about kernel 3.11.3? - it is the third release of Linux in 2011.

And? What a useless information.

BTW, it should be 3.2011.3, see Y2K.

#3 lore raw
Quoted 10 lines · ----- "Alexey Dobriyan
Quoted 4 lines · Artem S. Tashkinov

What can you say about kernel 2.6.32? Almost nothing.

What can you say about kernel 3.11.3? - it is the third release of Linux in 2011.

And? What a useless information.

BTW, it should be 3.2011.3, see Y2K.

Do you really believe Linux kernel will make it through 2100?

I bet by that time we will have some totally different hardware and software. Besides none of use will be alive by that time, so I don't see a problem. Besides, upon reaching 2100, if Linux still exists in its current form, the first digit could be increased to 4. :)

Best wishes,

Artem

#4 lore raw
In reply to Alexey Dobriyan
Quoted 10 lines · Alexey Dobriyan
Quoted 4 lines · Artem S. Tashkinov

What can you say about kernel 2.6.32? Almost nothing.

What can you say about kernel 3.11.3? - it is the third release of Linux in 2011.

And? What a useless information.

BTW, it should be 3.2011.3, see Y2K.
--

If you -really- wanna go that route - may as well be

20.11.3.18

century.decade.month.day .. that way we don't have problem until we
hit the year 10,000 ... :-)

g

#5 lore raw
Quoted 7 lines · Genes MailLists
Quoted 6 lines · Alexey Dobriyan
Quoted 4 lines · Artem S. Tashkinov

What can you say about kernel 2.6.32? Almost nothing.

What can you say about kernel 3.11.3? - it is the third release of Linux in 2011.

Quoted 8 lines
Quoted 4 lines

And? What a useless information.

BTW, it should be 3.2011.3, see Y2K.
--

  If you -really- wanna go that route - may as well be

     20.11.3.18

I think the reason day was excluded by previous suggestions is that the current development model doesn't generate a "blessed" version on anything close to a daily rate. Even if you wanted to incorporate the -rcs or -next into this scheme, it seems like it'd be somewhat problematic since the day field would drop in value during development e.g.
20.11.3.18 = 2.6.37-rc1
20.11.3.25 = 2.6.37-rc2
20.11.4.2 = 2.6.36-rc3

That having been said, <century>.<year>.<month> would be as valid as 3.<year>.<month>, and might help drive home the point that the version number is "a point in development" rather than some kind of "indicator of feature releases".

Quoted 3 lines

   century.decade.month.day .. that way we don't have problem until we hit the year 10,000 ... :-)

Or until the New Galactic Calendar is introduced... ;)

Silliness aside, what are the deficiencies of the current numbering that are being addressed here? The only things I can come up with are, "major number is getting too big" and "development no longer follows a major/minor feature based model, so the version numbering scheme should reflect this". Are there any other reasons for a change?

Kevin

Quoted 9 lines

 g
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/