lkml.org 
[lkml]   [2018]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectOn the kernel numbering scheme
Hello all,

I know this proposal has already been made great many times but I'd like
to repeat it and have a healthy discussion about it.

The current kernel numbering scheme makes no sense at all because the
first two numbers don't represent anything at all. They had some meaning
back in the 1.x 2.x 3.x days but then with the introduction of the new
rolling development model, they became worthless.

I'd love to change the kernel numbering scheme to this:

YYYY.RELEASE.PATCH_LEVEL

So that the first kernel to be released in 2019 will be numbered
2019.0(.0), and its consequent releases will be 2019.1, 2019.2, 2019.3,
etc. and its stable patches will be 2019.0.1, 2019.0.2, 2019.0.3,
2019.0.4, etc.

With this scheme you can easily see how fresh your kernel is and there's
no need arbitrary raise the first number because it always matches the
current year.

There's one minor detail which might raise some questions: there are
release candidates and then there's a release, so for the development
which starts before the year end we might start with e.g. 2018.5-rc1 and
then if the actual release crosses a new year mark we simply turn
2018.5-rc7 into 2019.0.0.

Best regards,
Artem S. Tashkinov

\
 
 \ /
  Last update: 2018-04-16 13:11    [W:0.034 / U:0.668 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site