Re: starting with 2.7

From: Bill Davidsen
Date: Mon Jan 03 2005 - 18:49:52 EST


Arjan van de Ven wrote:
On Mon, 2005-01-03 at 16:34 +0100, Adrian Bunk wrote:

On Mon, Jan 03, 2005 at 10:18:47AM -0500, Rik van Riel wrote:

On Sun, 2 Jan 2005, Andries Brouwer wrote:


You change some stuff. The bad mistakes are discovered very soon.
Some subtler things or some things that occur only in special
configurations or under special conditions or just with
very low probability may not be noticed until much later.

Some of these subtle bugs are only discovered a year
after the distribution with some particular kernel has
been deployed - at which point the kernel has moved on
so far that the fix the distro does might no longer
apply (even in concept) to the upstream kernel...

This is especially true when you are talking about really
big database servers and bugs that take weeks or months
to trigger.

If at this time 2.8 was already released, the 2.8 kernel available at this time will be roughly what 2.6 would have been under the current development model, and 2.6 will be a rock stable kernel.



as long as more things get fixed than new bugs introduced (and that
still seems to be the case) things only improve in 2.6.

The joint approach also has major advantages, even for quality:
All testing happens on the same codebase. Previously, the testing focus was split between the stable and unstable
branch, to the detriment of *both*.

You think so? I think the number of people testing the 2.4.xx-rc versions AND the 2.6.xx-bkN versions is a small (nonzero) percentage of total people trying any new release. I think people test what they plan to use, so there's less competition for testers than you suggest. People staying with 2.4 test that, people wanting or needing to move forward test 2.6.

--
-bill davidsen (davidsen@xxxxxxx)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
-
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/