But mostly the people who run production servers or fully featured
networking stuff use 2.0.X. On the Campus I run I use 2.0.X exclusively.
I patch 2.0.X with certain 2.1.X features if I need to have them.
Have tried to run a 2.1.X kernel during the burn-in phase of a new server
but quickly had to switch back to 2.0.X due to problems with networking.
I think it will be very difficult to release 2.2.x and to get a large
number of users to test it before release. There is not even much concern
to fix the existing bugs in 2.1.X (See the IP masquerading issue) . Many
people (like I) have or had to just give up on trying 2.1.X in a fully
featured environment.
I think the release time between stable kernels should be reduced
significantly. Release a stable kernel each 6 months at least and develop
a testing program. Keep the user base in touch with kernel development
otherwise we will loose momentum and users will not test the development
kernel anymore.
Recommendation:
For 2.2: Freeze, fix the bugs and get things out ASAP before trying any
new ideas that will break things again. It will be difficult to get 2.2.X
accepted since most people by this time are mostly satisfied with 2.0.X
kernels and have developed patches for 2.0.X if they need more
functionality.
Start 2.3.X for those people who cannot wait to experiment with new ideas.
Just my unhumble opinion....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu