On 9/12/06, Jim Cromie <jim.cromie@xxxxxxxxx> wrote:
I was looking for a bit more info here, so let me pose some addtions
on-list,
and see which are correct / improvements.
(mainline) ( implicit -dev suffix)
goal is to release every 8-12 weeks
1-2 weeks after release, new Current is opened.
1-2 weeks later, goes to -rc1
My undestanding is that the merge window for 2.6.X-rc1 begins
immediately when 2.6.X-1 is released. There are then two weeks for
major merges to occur before -rc1 should come out. This was part of
the plan to get the release cycle to be even *faster* than 8-12 weeks
(at this year's Kernel Summit, iirc). 2.6.18 was a bad example,
because Linus was out of town, so we had an extended -rc sequence.
-rcX
released as-needed, typically 1-2 weeks
starts slushy, as X increases, gets increasingly frozen
-mm
says ".. about to go into the 2.6 kernel .."
Not always ... at least not the "about to" part. Some patches stew for
months then are dropped.
Thanks
Nish
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
