Another way to resolve numbering issues

From: Jonathan Day
Date: Thu Mar 03 2005 - 14:43:46 EST


Hi,

I like the rapid cycling that Linux has switched to,
but I also like to know how stable something is. At
first sight, it's not obvious you can have both,
without the split trees that were causing headaches.

However, there may be an alternative, if there's any
agreement on testing. (There are validation suites and
validating compilers out there - earlier kernels went
through many a cycle of Stanford's compiler, if I
recall correctly.)

The suggestion is to put indicators of confidence in
the EXTRAS field for the kernel name. As an example,
let's say that kernel 2.6.15 is shown to be 75% clean
of likely problems, as a whole, but that there's a
variance of 10% from this mean value, when looking at
the individual modules. You really want a high value
to mean lots of confidence, so you actually want the
lack of variance, which is 100-10=90 in this case.

Your version number would then be: 2.6.15.75.90

That way, it doesn't matter if odd or even were
"stable", because you have a good idea of what the
stability is from those last two components. It also
cuts down on Linus' collection of Brown Paper Bags,
which will likely improve his family life.

Of course, there are no "simple" solutions, and this
is no exception. Sure, there are test suites and
validators, but what you'd need is a test suite or
validator that kernel developers as a whole would find
plausible, that can be updated fast enough to keep up
with the kernel changes and where the maintainers are
capable of learning enough about the different areas
to write tests that are even sensible. Because Linux
is written by coders (for the most part), such a
testing suite would also have to be simple enough,
fast enough and unobtrusive enough that coders would
actually use it.

IBM and SGI are involved in the Linux Testing Project,
and IBM has done a fair bit with getting SuSE through
the various EAL certifications, if rumors are to be
believed. Stanford has the validating compiler, as
I've mentioned. Assuming that the above concept isn't
shot down, disemboweled and fed to a cannibalistic
text editor, some combination of Linux hackers and the
above groups should be able to put together something
that would help identify if a kernel is stable or not.





__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/