Re: My thoughts on the "new development model"

Willy Tarreau
2004-10-27T05:14:29Z

On Wed, Oct 27, 2004 at 12:29:10AM -0400, Rik van Riel wrote:
> On Wed, 27 Oct 2004, Marcos D. Marado Torres wrote:
>
> > When it happened in 2.4 2.5 was created. Isn't all this just the
> > indication that we need a 2.6 development like 2.4 is, and we need 2.7
> > to be created?
>
> While a 2.7 series might provide developers with an "outlet"
> for their creativity, it does not give users the availability
> of the features they need.

Rik, "new features" are what causes the kernel to be in permanent development
mode. It happened to all of us that a new feature broke compatability with a
patch or even caused a side effect. Users don't "need" new features, they
*want* them. This is what makes them upgrade to the new release in a fast
release model. If 2.4 had been released sooner, USB would never have made
it in 2.2, and 2.2 users would have switched faster. I know people who still
use 2.2 only on their dev systems because they don't need any upgrade.

If you think that new features is something absolutely necessary, then we
could have a permanent 4-digit kernel version. The third one would indicate
new features, and the fourth one only bug fixes. One could be running
2.6.9.5 with 2.6.9 features and a few fixes. But I thought that was was the
2nd and 3rd digits already were for (the 2nd one is called "PATCHLEVEL").

> Most features are developed because a user needs them now,
> so having the users wait until 2.8 is not acceptable.

yes it would be acceptable if 2.8 was expected only half a year from now.

> Making
> the distributions backport the needed features into 2.6 leads
> to lots of duplicate effort and some code fragmentation.

I agree, and it also causes incompatibility between systems. I recently
sadly discovered that RHEL 3.0 was not "Linux" anymore, but "RHEL". With
all the 2.6 backports into 2.4, you cannot make it boot on a true 2.4
anymore. Very sad indeed.

Cheers,
Willy