Hi,
I am trying understanding how whole Kernel Release Cycle happens.
Below is my understanding followed with questions.

Say, the last released kernel is 2.6.26. Everyone takes that kernel and starts development for 2.6.27.
Now, Say person A and Person B have identified 2BUGS in scheduler algorithm. Both of them will create patch independently.
1. Then, whom should they send these patches ? To Linus ? Now, what if Person A's patch and Person B's patch depends on each other. which means if I apply Person A's patch first then Person B's patch gets Hunked Failed and Vice Versa.

2. Then there will be intermediate releases like 2.6.27-RC1 and 2.6.27-RC2 and so on...... and then 2.6.27 Final Release. How many RC releases happen in general ?

3. Say, I found that just 5 minutes before, 2.6.27-RC3 release happened. Now, my further development should be based on 2.6.27-RC3. How can I get that latest source ? Is it better to get from Kernel.org OR from git URL ?

Thanks,

This is how I see it - no guarantee that it's correct.
Each portion of the kernel has a maintainer - it is part of their job to co-ordinate submitted patches. Then they go up the tree to Andrew Morton and his -mm releases.

Linus' tree is the end of the line - he gets to see the amalgamation of everyone elses' work. As for release candidates, they seem to be (to some extent) arbitrary.

Forgot 3): I just pull the later -RC patch and apply that. They are cumulative, so you need to revert the previous level first. All in ../Documentation.