| |||||||||||||
Bypassing linux-nextBypassing linux-nextPosted Jan 20, 2011 16:34 UTC (Thu) by kirkengaard (subscriber, #15022)Parent article: Bypassing linux-next
"Those developers will need to either get their own trees into linux-next (an easy thing to do) or take the complaints when code which lived in -mm is seen by testers for the first time when it hits the mainline."
Odd, I was of the impression that the whole point of -mm was that it let people use code and test it before it was shipped upstream. Have we deprecated that code path?
(Log in to post comments)
Bypassing linux-next Posted Jan 20, 2011 17:42 UTC (Thu) by nevets (subscriber, #11875) [Link]
linux-next is suppose to take over that role. But it is only to have things that are considered ready for upstream. Not at the redesign phase. -mm can have things still being redesigned. Perhaps what is needed is to have the new features that finally have a stable design to move from -mm to linux-next. And then from linux-next to mainline.
I guess this means that Andrew's work flow should go to linux-next and after a bit of time, that same code can go to Linus.
|
|||||||||||||