We number the kernel based on the year, and the numbers of releases we
have done this year:
For example, the first release in 2009 would be called:
If we want to be a bit more "non-zero-counting" friendly: we can start
at "1" for the number:
2009.1.0 for the first release
2009.2.0 for the second.
Then the stable releases can increment the minor number:
2009.1.1 for the first stable release
2009.1.2 for the second.
and so on.
Benefits of this is it more accuratly represents to people just how old
the kernel they are currently running is (2.6.9 would be have been
2004.9.0 on this naming scheme.)
Yes, we can handle the major/minor macros in the kernel to provide a
compatible number so that automated scripts will not break, that's not a