Greg K-H Recommends New Kernel Version Naming

Kroah-Hartman writes that he had meant to bring up his suggestion at the Kernel Summit 2008 in September that he does now as a follow-up. He had always been involved with version numbering and finds the current scheme unmanageable.

His recommendation: future versions of the Linux kernel should follow the pattern four_digit_year.release_number.minor_release_number. By this pattern the first release in the coming year would be 2009.0.0, the second 2009.1.0, and so forth. If zero-numbered releases are undesirable, he says, the year could also begin with release 2009.1.1.

Kroah-Hartman points out that the naming scheme provides a better way to determine how old the release is. Kernel 2004.9.0 would be easier to date than Kernel 2.6.9.

The current scheme follows the pattern 2. major_release.minor_release.extra_version. With the new scheme, kernel macros with major and minor numbers would also have compatible naming so as not to break scripts, he assures the community in his email.

Among the first responses was one from H. Peter Anvin who found it easiest just to increment the last digit, such as 27, 28, 29, etc. He finds the existing prefix 2 with the large following digits to have "outlived its utility" and suggests bumping the version to 3.0 and maintaining that scheme for "huge changes."

Adrian Bunk had rather a different view and warned against radical changes that could affect not only the Kernel and its tools, but break countless userspace programs. Many of these programs interpret the kernel version number through calls such as uname -r. He gives a snippet from an OpenSSL library script as an example.