Tightening the merge window rules [LWN.net]

Tightening the merge window rules

Posted Sep 11, 2008 8:02 UTC (Thu) by dlang (✭ supporter ✭, #313)
Parent article: Tightening the merge window rules

the real cutoff isn't at the end of -rc1, Linus frequently pulls things in from Andrew in -rc2, and sometimes puts patches that he things likely to conflict with other changes in -rc1 so that people get a cheap bisect-like test to see which one causes the problem

it's usually around -rc3 that the changes really stop.

the other thing is that not all regressions get documented as such.

documented regressions are usually when a person finds the problem and needs to report it for others to research. if the developer finds the problem they just send a patch and explain why it's a regression, they don't waste their time to submit a regression report.

(Log in to post comments)

breakout by -rc number?

Posted Sep 12, 2008 1:35 UTC (Fri) by kirkengaard (subscriber, #15022) [Link]

Good point -- it might be instructive to see a chart like is in the article for -rc1/post-rc1, broken down by specific -rc number. If -rc1 and -rc2 contain what one might expect, with occasional lapses into -rc3, that might be a more manageable result to deal with.