RE: RFD: Kernel release numbering

Hua Zhong
2005-03-03T22:02:17Z

> In other words, I'm really talking about something different
> from what you seem to envision.

Indeed. What I have in mind (and suggested in the past) is that we have a
real 2.6 stable release maintainer. The only difference is that he starts
from a random 2.6.x release he picks, and releases 2.6.x.y until he thinks
stable enough, and he moves on to another 2.6.z release and start the same
work. He decides which 2.6.x to pick for the next stable release. Alan Cox
has expressed his interest in this during the last discussion but it seems
you didn't pay attention or care.

The reason that I think it's important for some other person to do this job
independently is that you are not bothered by bugfixes, which you never did
well. :) You move on to each release as you do today, with different
criteria, and someone else who can do the job better do so to stablize it.

In the end it's more like the old way of 2.5/2.4, but just with a shorter
release cycle, and the "2.6 stable release maintainer" could also continue
to pick up new 2.6.x releases to work on instead of having to be stuck on
one tree for 2 years or ever. He can say "this is the last 2.6.12.x release
and next I'll start 2.6.16.1", etc.

For this to happen the person has to be well-recognized and trusted by the
community. Alan is one of the best candidates. :) Of course, I'm not sure if
he is still interested..

Hua