Jesper Juhl wrote: > > The normal way -stable works is that it tracks the latest 2.6.x kernel > that has been released. > Now that 2.6.21 has been released, a final flush of the patch queue > against 2.6.20 is done, that will be 2.6.20.10, and then -stable will > switch to 2.6.21.y, when 2.6.22 comes out a final 2.6.21.y is made and > then it's off to track 2.6.22 >
The older stable version is usually maintained for a while after the next major release comes out. How long that is can vary. I would personally like to see 2.6.20 continue for a while, at least until 2.6.21.x is judged stable enough (that could be a long time.) - 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/
