It turns out there 43 different people who had a voice in the feature, which was hashed out over a series of grinding meetings involving teams responsible for kernel, shell, Tablet PC, Longhorn, and (drumroll please) "Windows Mobile PC User Experience"."
"In Windows, the [repository] node I was working on was 4 levels removed from the root. The periodicity of integration decayed exponentially and unpredictably as you approached the root so it ended up that it took between 1 and 3 months for my code to get to the root node, and some multiple of that for it to reach the other nodes."
http://moishelettvin.blogspot.com/2006/11/windows-shutdown-c...
Does it take less time for a patch to the graphic system (for example) to trickle up to the Linus' tree? And to end up in an LTS distro?
http://mcis.polymtl.ca/publications/2013/msr_jojo.pdf
What percentage of submitted patches has been integrated successfully, and how much time did it take? Around 33% of patches are accepted. Reviewing time has been dropping down to 1–3 months, while integration time steadily has been increasing towards 1–3 months, bringing the total time to 3–6 months.
That's based on 8 years of data.
has a few passages that illustrate how that startegy helped Microsoft Excel trounce Lotus 123 plus chat wars won by AOL around that time.
http://www.joelonsoftware.com/articles/fog0000000052.html and http://www.joelonsoftware.com/articles/fog0000000056.html
It was pretty painful. A feature I was involved with got nixed by the Compliance team due to concerns around backwards compatibility. They had no incentive to say Yes, either, since that would mean more work for them.