Some development statistics for 2.6.27
Some development statistics for 2.6.27
Posted Oct 10, 2008 15:55 UTC (Fri) by aegl (subscriber, #37581)In reply to: Some development statistics for 2.6.27 by iabervon
Parent article: Some development statistics for 2.6.27
"There's no reason that most of the changes for 2.6.x should be in 2.6.x-rc1"
The current kernel development model is that all new code for the next release be merged during the two week merge window. It should have been submitted before the merge window so that it see some test time in linux-next or -mm, and so that merge and integration issues are sorted out before being sent to Linus. Post-rc1 is supposed to be for bug-fixes and regression. I don't think that those should require 45% of the code changes that were needed for the original features (if they do, it would seem to indicate that the features were not really ready to be merged).
At this year's kernel summit Linus admitted to being a big softie when it comes to accepting merges after -rc1 ... it seems that developers are taking advantage of this more and more each release.
