Who's writing 2.6.21 and related issues

Posted Mar 9, 2007 8:44 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]

well, we have releases, with release candidates between them, daily snapshots of Linus' git tree, and the raw git tree itself (updated frequently by Linus, but not on a fixed schedule)

we have make targets of allyesconfig, allnoconfig, allmodconfig, randconfig (among others) to make the job of automating tests easier

we have sets of systems that work to compile lots of sets of options from the release candidates (and if they have time, daily snapshots)

what more do you think needs to be done?

remember, the problem isn't that the change breaks things for everyone, it can break something for someone with some combination of compile options. the number of combinations to compile to cover every possibility is far too high to take place in the real world (how many years do you want to wait betwen when development stops and testing begins before a release is made?

the thing that helps is people with different requirements testing at least the release candidates. while it doesn't garentee that there won't be any problems, the more combinations that get tested the more bugs get found early (and the earlier a group/originization runs tests with their requirements, the earlier any bugs that would affect them get found and fixed)

Posted Mar 10, 2007 15:39 UTC (Sat) by dankohn (subscriber, #6006) [Link]

Take a look at Martin Bligh's http://test.kernel.org/.