On 15 Jul 2005 02:38:58 +0200, Andi Kleen <[EMAIL PROTECTED]> wrote: > Mark Gross <[EMAIL PROTECTED]> writes: > > > > The problem is the process, not than the code. > > * The issues are too much ad-hock code flux without enough > > disciplined/formal > > regression testing and review. > > It's basically impossible to regression test swsusp except to release it. > Its success or failure depends on exactly the driver combination/platform/BIOS > version etc. e.g. all drivers have to cooperate and the particular > bugs in your BIOS need to be worked around etc. Since that is quite fragile > regressions are common. > > However in some other cases I agree some more regression testing > before release would be nice. But that's not how Linux works. Linux > does regression testing after release. > And who says that couldn't change?
In my oppinion it would be nice if Linus/Andrew had some basic regression tests they could run on kernels before releasing them. There are plenty of "Linux test" projects out there that could be borrowed from to create some sort of regression test harness for them to run prior to release. It would be super nice if they had a suite of tests to run and could then drop a mail on lkml saying 2.6.x is almost ready to go, but it currently fails regression tests #x, #y & #z, we need to get those fixed first before we can release this - and then every time a bug was found that could resonably be tested for in the future it would be added to the regression test suite... That would lead to more consistent quality I believe. -- Jesper Juhl <[EMAIL PROTECTED]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/