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..
I think the system we appear to have wound up with is superior: there is no single 2.6.X.Y maintainer, but more a $sucker mail alias that Does The Right Thing.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/