On Apr 25 2007 20:29, Linus Torvalds wrote: > >If the goal for 2.6.20 was to be a stable release (and it was), the goal >for 2.6.21 is to have just survived the big timer-related changes and >some of the other surprises [...] So it's been over two and a half >months, and while it's certainly not the longest release cycle ever, it >still dragged out a bit longer than I'd have hoped for and it should >have.
I really appreciate the lot of -rcs, especially if there are so many intrusive changes/regressions. Like Andrew, I have a feeling that it gets buggier, but at least, it seems to be made up every ... two releases. 2.6.16 was a good one, .18, and .20. I suppose the bug/regression distribution between [2.6.16-2.6.17, 2.6.17-2.6.18] was biased like [70, 50]. About 2.6.21 - will see, rc has been to my liking. Since a picture says more than a thousand words, have http://jengelh.hopto.org/GFX0/kernel-rating-2.6.21.png (The last kernel to have only 5 -rcs was 2.6.14 - interesting) Happy hacking, Jan -- - 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/
