Re: RFD: Kernel release numbering

[Adrian Bunk]

On Thu, Mar 03, 2005 at 02:15:06AM -0800, Andrew Morton wrote:
> Jeff Garzik <jgarzik@xxxxxxxxx> wrote:
> >
> > We need to not only produce a useful kernel, but also package it in a 
> >  way that is useful to the direct consumers of the kernel:  distros 
> >  [large and small] and power users.
> 
> This comes down to the question "what are we making"?  Is it an end
> product, or is it a technology which can be turned into an end product? 
> Because the two are different things.
> 
> I'd say that mainline kernel.org for the past couple of years has been a
> technology, not a product.
>...

Even-numbered kernels started becoming a product after the next 
odd-numbered kernel series started.

2.4 might have it's limitations, but today it's a pretty good product.

> But there's something else:
> 
> I would maintain that we're still fixing stuff faster than we're breaking
> stuff.  If you look at the fixes which are going into the tree (and there
> are a HUGE number of fixes), many of them are addressing problems which have
> been there for a long time.
> 
> So as long as we remain in this state, we don't need to do anything.  The
> technology gets closer to a product until we reach the stage where the
> fixage rate equals the breakage rate.   And we're not there yet.
> 
> (It's nice that patches are called "fix the frobnozzle gadget", but this
> analysis would be a lot easier if people would also label their patches
> "break the frobnozzle gadget" when that's what they do.  Oh well).
> 
> So I'd suspect that on average, kernel releases are getting more stable. 
> But the big big problem we have is that even though we fixed ten things for
> each one thing we broke, those single breakages tend to be prominent, and
> people get upset.  It's fairly bad PR that Dell Inspiron keyboards don't
> work in 2.6.11, for example...
> 
> And people will incorrectly (and even wildly) generalise as a result of
> such silly little isolated bugs.  We can wholly address such problems with
> a 2.6.x.y productisation series.

The point behind this is:

It's not the most important question for a user whether the total number 
of bugs has decreased or increased.

The most serious problems for users are regressions compared to the 
kernel before.

If a user who is happily using 2.6.8 learned that "stable" kernel 2.6.9 
broke driver A for him and "stable" kernel 2.6.10 broke driver B for 
him, he will not try any new "stable" kernel simply because it only 
causes trouble for him.

Bad luck, if he therefore misses some serious security fix.

And yes, there are many people out there who use for many different 
reasons self-compiled kernels.

> And something else:
> 
> I don't think 2.2 and 2.4 models are applicable any more.  There are more
> of us, we're better (and older) than we used to be, we're better paid (and
> hence able to work more), our human processes are better and the tools are
> better.  This all adds up to a qualitative shift in the rate and accuracy
> of development.  We need to take this into account when thinking about
> processes.
> 
> It's important to remember that all those kernel developers out there
> *aren't going to stop typing*.  They're just going to keep on spewing out
> near-production-quality code with the very reasonable expectation that
> it'll become publically available in less than three years.  We need
> processes which will allow that.
>...

The traditional solution was to have a development series for the 
developers who don't stop typing and a stable series with few 
regresssions.

Until now, it seems 2.6 has too many regressions in every new released 
kernel for being a really stable kernel.

And people aren't dumb - you can't fool them with any version number 
games. People have learned that a -rc by Linus is equivalent to a -pre 
release by Marcelo. And they will quickly learn that a 2.6.<even> 
kernel will be equivalent to a -pre releaese by Marcelo.

What about thinking instead how to get a 2.7 cycle that roughly fits 
everyones needs?

It took two years from 2.5.0 to 2.6.0 .
That was long. Let's try to shorten it.

Make the feature freeze half a year after the start of 2.5 instead of 
one year as was done in 2.5 . This cuts off half a year of the two 
years. Yes, it really cuts off half a year, because the first year of 
2.5 also included half a year of IDE changes where even the bravest 
kernel developer didn't dare to test the kernel.

Perhaps there are also ways how the more developers, better tools and 
processes can help in shortening the one year after halloween.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/