Jim Cromie wrote:
I was looking for a bit more info here, so let me pose some addtions
on-list, and see which are correct / improvements.
Thanks for doing this. Improvements to the wiki are always
welcome. Lets help people understand how Linux kernel
development works...
(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
-rcX
released as-needed, typically 1-2 weeks
starts slushy, as X increases, gets increasingly frozen
Looks good. Maybe tell people that this is not really a tree,
but part of the process through which the 2.6 kernel goes to
make new releases.
In fact, maybe the VariousKernelTrees page would be a good
page to explain how the 2.6 kernel process works?
-mm
says ".. about to go into the 2.6 kernel .."
can we get more specific ?
- typically has 1000 .. 1900 patches
- most are to be considered for Current-rc + 1 or + 2
- intended for wider testing, and to identify interaction with other
patches
- some (small %, mostly new drivers) get into Current-rc, before its
released (Andrew and Linus decide)
- occaisionally big work goes thru -mm, and into -rcX w/o +1 release
gestation
lockdep, sema --> mutex switch (these 2 examples matured in
-rt 1st)
- max changes usually-rate is mostly
Looks good. Maybe also tell people that code that does not
get fixed often gets dropped from -mm again without going
into the upstream kernel?
24-ac
major product of this tree was VM that went into 2.4.10
Ironically, the 2.4-ac tree stabilized the VM that was removed
in 2.4.10...
24-rmap
reverse mapping was merged into 2.4.??
Nope, it got merged into 2.5.
--
What is important? What you want to be true, or what is true?
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
