Stability is a relative term. Ten patch levels in 4 months doesn't yet equal
"stable" in my mind, no matter what the "official" classification of 2.2.x
is. So I imagine that 2.0.37 is a modest, incremental upgrade to 2.0.36,
intended for use on older systems that are being used in production
environments, machines that can't be offline or risk kernel instability for
any substantial period (and that probably don't take advantage of the 2.2.x
improvements anyway).
I do know that Slackware (probably the most conservative of the commercial
distributions about making fundamental changes) is releasing version 3.9 --
its last 2.0.x version -- simultaneously with 4.0 -- its first 2.2.x version.
At 02:28 AM 6/15/99 +0300, Raider wrote [in part]:
> Hi!
> One stupid theorectical question. So we have a new stable
>kernel. The 2.2.x series. And it getts better and better - the
>10th patch level.
...
> And now here it goes the question: why 2.0.37? This
>question arised a couple of moments when I was checking my private
>mails - kernel announce is consderet to be part of private mails -
>and saw that both 2.0.37 and 2.2.10 are out.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA 94303-3603 [EMAIL PROTECTED]
----------------------------------------------------------------
