If I get at least 5 people in favor of such a list, I'll
immediately create linux-wish@nl.linux.org (or kernel-devel
or some other, better name).
> I'd really like to know what you believe to be the main-issues that we
> need to deal with in v2.3, and what the schedule should be for it.
>
> Personally, I think that the development time for v2.3 must be
> significantly shorter than the one for v2.1, and more focused on a
> narrow set of important improvements, apart from obvious bugfixes
> and new drivers.
One of the ways in which the 2.3 cycle can be shorter is
by only integrating stuff that's already being worked on
and is ready by the time 2.3.0 is forked off. Then we
integrate all those things within 5 revisions and start
debugging. Maybe we even want to distribute all of those
things in one big patch _before_ 2.3.0 is forked off.
Anyway, the last thing we should do is keeping Linus from
his far-more-important 2.2 work...
regards,
Rik -- If a Microsoft product fails, who do you sue?
+-------------------------------------------------------------------+
| Linux memory management tour guide. riel@nl.linux.org |
| Scouting Vries cubscout leader. http://www.nl.linux.org/~riel |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/