RE: My thoughts on the "new development model"

["Hua Zhong" <hzhong@cisco.com>]

> On Maw, 2004-10-26 at 17:58, Hua Zhong wrote:
> > The fact is, these days nobody wants to be a stable-release 
> >maintainer anymore. It's boring.
> 
> That depends what kind of an engineer you are. Just as there 
> are people who love standards body work and compliance 
> testing/debugging there are people who care about stable trees.

Absolutely agreed. There are folks around me who can do one thing much
better than the other.

When I said "nobody", I really meant "top kernel developers". I have not
seen anyone step up and say "I'll volunteer to maintain a 2.6 stable
release" hence the comment.

This is actually not a problem caused by the new development model per se.
The same thing might have happened with 2.4. You know what I'm talking
about. Most talented people just like new challenges instead of maintaining
old code.

However, there are some things that make this situation worse by the new
model.
1. No official stable releases and thus no official maintainers. 2.6 is no
longer a stable release. 2.6.x might be. And Linus doesn't seem to plan to
endorse anyone for this job. Previously, Linus could appoint someone and
even if he is not really well-known, people would eventually accept him, but
now it's not the case anymore. More importantly, if there is no official
stable releases, whom do other people send bug fixes to? From both user and
developer perspective, this is very hard to work out.

2. The new version scheme. Now a stable release has to be 2.6.x. So instead
of being a 2.6 maintainer, you might be called a 2.6.x maintainer. One extra
number, less importance and recognicion, and less motivation for volunteers
to show up (especially for relatively new people). Just common psychology.
:)

These are just my observations. As far as I can see only two things will
help:
1. Appoint an official 2.6 maintainer. Be it someone Linus appoints, or
someone like Alan Cox who volunteers. :-)
2. This maintainer will not be stuck at only one 2.6.x version. Instead, he
maintains 2.6.x for a while until it is stable enough, and then move up to
2.6.y (y>x), and start the stabilization again.

Hua